{"action":"closed","issue":{"url":"https://api.github.com/repos/inverse-inc/packetfence/issues/1433","repository_url":"https://api.github.com/repos/inverse-inc/packetfence","labels_url":"https://api.github.com/repos/inverse-inc/packetfence/issues/1433/labels{/name}","comments_url":"https://api.github.com/repos/inverse-inc/packetfence/issues/1433/comments","events_url":"https://api.github.com/repos/inverse-inc/packetfence/issues/1433/events","html_url":"https://github.com/inverse-inc/packetfence/issues/1433","id":151339568,"number":1433,"title":"Timeout in systemd service file too short","user":{"login":"MarieHo","id":17873538,"avatar_url":"https://avatars.githubusercontent.com/u/17873538?v=3","gravatar_id":"","url":"https://api.github.com/users/MarieHo","html_url":"https://github.com/MarieHo","followers_url":"https://api.github.com/users/MarieHo/followers","following_url":"https://api.github.com/users/MarieHo/following{/other_user}","gists_url":"https://api.github.com/users/MarieHo/gists{/gist_id}","starred_url":"https://api.github.com/users/MarieHo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/MarieHo/subscriptions","organizations_url":"https://api.github.com/users/MarieHo/orgs","repos_url":"https://api.github.com/users/MarieHo/repos","events_url":"https://api.github.com/users/MarieHo/events{/privacy}","received_events_url":"https://api.github.com/users/MarieHo/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-27T09:27:02Z","updated_at":"2016-06-23T18:06:14Z","closed_at":"2016-06-23T18:06:14Z","body":"Hello,\r\nwe are experiencing some issues with packetfence installed from DEBIAN repositories.\r\nIt seems at the first start the timeout specified in systemd file is too short, here is what we can see in systemd status:\r\n\r\n> ● packetfence.service - PacketFence Service\r\n>    Loaded: loaded (/lib/systemd/system/packetfence.service; enabled)\r\n>    Active: failed (Result: timeout) since Wed 2016-04-27 08:57:54 UTC; 2s ago\r\n>   Process: 953 ExecStart=/usr/local/pf/bin/pfcmd service pf start (code=killed, signal=TERM)\r\n\r\nWe launched startup command using time: time /usr/local/pf/bin/pfcmd.pl service pf start\r\nHere is the output:\r\n\r\n```\r\n[...]\r\nradsniff|start\r\n[ most of time is lost between these two lines]\r\nhttpd.graphite|start\r\n\r\nreal\t12m23.111s\r\nuser\t0m44.612s\r\nsys\t0m1.596s\r\n```\r\nObivously the \"TimeoutStartSec=180s\" specified in \"/lib/systemd/system/packetfence.service\" is not enough.\r\n\r\npacktfence.log show that both service took normal time to start but I have no clue what's happening between them:\r\n\r\n> Apr 27 09:03:16 pfcmd.pl(1470) INFO: Daemon radsniff took 0.044 seconds to start. (pf::services::manager::launchService)\r\n> Apr 27 09:14:44 pfcmd.pl(1470) INFO: Daemon httpd.graphite took 0.030 seconds to start. (pf::services::manager::launchService)\r\n\r\nAfter the first start it's a lot faster and complete startup now fits into the 180s frame.\r\nHere is the time for the second start:\r\n```\r\ntime systemctl start packetfence\r\n\r\nreal\t1m6.068s\r\nuser\t0m0.000s\r\nsys\t0m0.000s\r\n```\r\n\r\nThank you\r\n"}}
{"actor":{"display_login":"whitx"}}