Ok, I set the bug to invalid then.
We might still have collected a nice set of info for the next one to stumble
over this.
So thank you for your work with me on thie Marius!
** Changed in: xinetd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you ar
Yes, etckeeper shows that xinetd was installed in a separate apt
transaction, after cups-bsd. Both happened in 2009.
I suspect I don't need lpd compatibility -- I expect any users who use
the print queue access it over IPP. I think I'll remove xinetd entirely
and forget about this issue.
--
Yo
I had no cups-bsd package yet (not pulled in by dependencies anymore), but even
if I had this is not set (by default) anymore
db_get cups-bsd/setuplpd
So it didn't trigger for me.
$ echo "set cups-bsd/setuplpd true" | debconf-communicate
$ apt install --reinstall cups-bsd
Now I see the code y
Yes, this system has been continuously upgraded from older Ubuntu
versions (starting with 9.04). It acts as a print server for the
office. I've no memory of manually setting up xinetd for cups-lpd. I
always assumed it was pulled in automatically as a dependency.
/etc/xinetd.d/printer looks like
1. cups installed
still behaes as above
2. set up cups-lpd as in [1]
BTW this could be an artifact from the migration to systemd
It actually mentions there should be systemd services but I haven't found one
actually.
I only found /lib/systemd/system/cups.service (for IPP), but no LDP one.
So for
Hmm, in a pure (no xinetd service configured, just installed xinetd) it
does not show the issue you described:
# ps axlf | grep xinetd
0 0 13268 12676 20 0 14620 1012 pipe_w S+ ? 0:00 \_ grep
--color=auto xinetd
1 0 13227 1 20 0 15056 2120 poll_s Ss ?
The last line of the log excerpt has a suspiciously low PID number
Feb 16 07:03:30 fridge xinetd[2756]: Exiting...
I took that to be a clue that this is the old instance of xinetd, that
was supposed to be stopped by the two lines above:
Feb 16 07:03:29 fridge xinetd[24720]: * Stopping in
In case this might be relevant: the only service xinetd is serving on
this machine is /usr/lib/cups/daemon/cups-lpd (via
/etc/xinetd.d/printer).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750387
T
Hi Marius,
logs are scarce on this :-/
The attached journal is of two days after the incident for example.
Where do you derive "so it looks like systemd is trying to start the new
process before the old one finishes exiting." from.
I see
1. * Stopping internet superserver xinetd
...done.
2.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since there isn't enough information in your report to differentiate
between a local configuration problem and a bug in Ubuntu, I'm marking
this bug as Incomplete.
If indeed this is a local configuration problem,
10 matches
Mail list logo
