Re: I can start my tracker from command line, but it does not start as a daemon...
Ed Trumbull <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.user |
|---|---|
| Message-ID | <PH7PR12MB56564B0B2AAD987E8FFB6E38843E9@PH7PR12MB5656.namprd12.prod.outlook.com> |
Specifying the -l option on the command line appears to have worked, thanks. I thought that specifying the filename in the [logging] section of config.ini would suffice, and that specifying -l would be redundant. For now, I have both the filename option in the config.ini and the -l option on the command line pointing to the same file. Is there an advantage to having them point to different files? ________________________________ From: [email protected] <[email protected]> on behalf of John P. Rouillard <[email protected]> Sent: Wednesday, November 9, 2022 11:15 AM To: Ed Trumbull <[email protected]> Cc: [email protected] <[email protected]> Subject: Re: [Roundup-users] I can start my tracker from command line, but it does not start as a daemon... Hi Ed: In message <PH7PR12MB5656D94374E0747B42F932DE843E9@PH7PR12MB5656.namprd12.prod. outlook.com>, Ed Trumbull writes: >server is a VM running linux mint 21 (linux 5.15.0-52-generic) >Roundup version is 2.2.0 >Python 3.10.6 >All patches to the system are in place. > >If I run this command from the command line: >/usr/local/bin/roundup-server -n 0.0.0.0 -p 8917 -C /local/data/roundup/as2it/config.ini > >the server starts happily and I can access it. > >If I try to make it a daemon by running this: >sudo /usr/local/bin/roundup-server -n 0.0.0.0 -p 8917 -d /run/roundup/as2it.pid -C /local/data/roundup/as2it/config.ini > >I don't see any errors, either in the syslog or on the command line, the >pid file is updated with a new pid, but the daemon doesn't start. > >Where should I look to find out why? The man page for roundup-server says: -l file Sets a filename to log to (instead of stdout). This is required if the -d option is used. Please add -l /path/to/file/writable/by/user/running/roundup-server to the command line. My guess is the server is exiting because it fails to open a log file. But by that time, roundup-server has disconected from the terminal so the error gets lost. I've opened a ticket to have roundup-server complain of -d is used without -l. https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.roundup-tracker.org%2Fissue2551238&data=05%7C01%7CEdT%40as2inc.com%7Cecd6b70bd59f4279b72208dac26dab4b%7C5287874e6a4b4ad48e3faf2630161633%7C0%7C0%7C638036073526319591%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xr9gCtEWsIamw08HCt9ANvswWBmCH6rMz43UCBAWjxc%3D&reserved=0 Also since you are on mint/ubuntu/debian you might want to run roundup-server under systemd. See: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Froundup%2Fcode%2Fci%2Fdefault%2Ftree%2Fscripts%2Fsystemd.gunicorn&data=05%7C01%7CEdT%40as2inc.com%7Cecd6b70bd59f4279b72208dac26dab4b%7C5287874e6a4b4ad48e3faf2630161633%7C0%7C0%7C638036073526319591%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GPHSTAwBho%2Bwl0KCnzPfrGCKE%2BnhNgJWxUxwGtL3t2Q%3D&reserved=0 for a sample systemd unit file. Change out the ExecStart with your command line without the -d or -l options. (Systemd will captue the output to stdou and make it available via journalctl.) Also remove the ExecReload setting (I think ExecStop/ExecStart is used if there is no ExecReload but I may be wrong on that). How is roundup working for you other than this? Have a great rest of the week. -- -- rouilj John Rouillard =========================================================================== My employers don't acknowledge my existence much less my opinions. _______________________________________________ Roundup-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/roundup-users