You are not logged in.
I don't know if this issue is a bug or if I'am doing something terribly wrong.
I've installed ArchLinux without GUI, just base, as a pure printserver a few weeks ago with only cups running and it worked.
But when I try to do exactly the same installation again on same PC (tried IPFire meanwhile) it is a mess!
First CUPS suddenly needs avahi to be running (enabled).
Without it, I get a 'core-dump' error:
systemd-coredump[###]: Process 255 (cupsd) dumped core.
systemd[1]: cups.service: main process exited, code=dumped, status=6/ABRTNext cups does not start, does not offer shared printers and is not accessible through web interface until I start it manually.
Than everything works as supposed.
On reboot: same procedure!
Of course I edited 'cupsd.conf' on the server, added
Listen *:631
and
Allow from 192.168.XXX.XXX/24
to all <Loaction> entries.
Though I enabled cups (which in fact only enables the cups.socket) I do not get it to work.
So it seems to be a problem with this non reacting cups.socket, perhaps?
BTW: sshd.socket works.
There are no errors which I could post.
I've also reinstalled serveral times...
PS:
Menawhile I found a workaround:
# systemctl disable cups
# sudo ln -s '/usr/lib/systemd/system/cups.service' '/etc/systemd/system/multi-user.target.wants/cups.service'
but I still wonder, why the intitial configuration which worked till a few days suddenly stopped working...
Last edited by renegat (2013-02-27 14:28:14)
Offline
I don't know if this issue is a bug or if I'am doing something terribly wrong.
I've installed ArchLinux without GUI, just base, as a pure printserver a few weeks ago with only cups running and it worked.
But when I try to do exactly the same installation again on same PC (tried IPFire meanwhile) it is a mess!First CUPS suddenly needs avahi to be running (enabled).
Without it, I get a 'core-dump' error:systemd-coredump[###]: Process 255 (cupsd) dumped core. systemd[1]: cups.service: main process exited, code=dumped, status=6/ABRTNext cups does not start, does not offer shared printers and is not accessible through web interface until I start it manually.
Than everything works as supposed.
On reboot: same procedure!
Of course I edited 'cupsd.conf' on the server, addedListen *:631
and
Allow from 192.168.XXX.XXX/24to all <Loaction> entries.
Though I enabled cups (which in fact only enables the cups.socket) I do not get it to work.
So it seems to be a problem with this non reacting cups.socket, perhaps?
BTW: sshd.socket works.There are no errors which I could post.
I've also reinstalled serveral times...
PS:
Menawhile I found a workaround:# systemctl disable cups
# sudo ln -s '/usr/lib/systemd/system/cups.service' '/etc/systemd/system/multi-user.target.wants/cups.service'but I still wonder, why the intitial configuration which worked till a few days suddenly stopped working...
Using the .socket will activate cups on access. Which is much better than keeping it running all the time. Unless you want it running all the time.. Up to you.
I'm curious what your cups.service acutally looks like.. since you shouldn't be having to make a symlink manually.. That's what systemctl enable is for, as you probably know. And why not paste the socket too while you're at it.. Mine are at the bottom of this reply. I also added the cups.path so you can compare and see if anything went wrong there.. Mine works great on 3.7.9-1 kernel.
I'm not sure why you're linking cups.service to multi-user.target.wants/ but it should be WantedBy=printer.target.. Have a look below.
* enabling cups.service should create symlinks for the service unit and the path
* enabling cups.socket should only create the symlink for the socket.
╰─╼ cat cups.socket
[Unit]
Description=CUPS Printing Service Sockets
[Socket]
ListenStream=/var/run/cups/cups.sock
[Install]
WantedBy=sockets.target╰─╼ cat cups.service
[Unit]
Description=CUPS Printing Service
[Service]
ExecStart=/usr/sbin/cupsd -f
PrivateTmp=true
[Install]
Also=cups.socket cups.path
WantedBy=printer.target╰─╼ cat cups.path
[Unit]
Description=CUPS Printer Service Spool
[Path]
PathExistsGlob=/var/spool/cups/d*
[Install]
WantedBy=multi-user.targetaur::dotshare.it::blog
"Stay true."
Offline
Thank you for your reply, cinelli.
Using the .socket will activate cups on access. Which is much better than keeping it running all the time. Unless you want it running all the time.. Up to you.
Well, it's a printserver so it dosen't really matter.
This is what happens when enabeling cups.service:
[root@printserver ~]# systemctl enable cups.service
ln -s '/usr/lib/systemd/system/cups.service' '/etc/systemd/system/printer.target.wants/cups.service'
ln -s '/usr/lib/systemd/system/cups.socket' '/etc/systemd/system/sockets.target.wants/cups.socket'
ln -s '/usr/lib/systemd/system/cups.path' '/etc/systemd/system/multi-user.target.wants/cups.path'/etc/systemd/system/sockets.target.wants/cups.socket:
[Unit]
Description=CUPS Printing Service Sockets
[Socket]
ListenStream=/var/run/cups/cups.sock
[Install]
WantedBy=sockets.target/etc/systemd/system/printer.target.wants/cups.service
[Unit]
Description=CUPS Printing Service
[Service]
ExecStart=/usr/sbin/cupsd -f
PrivateTmp=true
[Install]
Also=cups.socket cups.path
WantedBy=printer.target/etc/systemd/system/multi-user.target.wants/cups.path
[Unit]
Description=CUPS Printer Service Spool
[Path]
PathExistsGlob=/var/spool/cups/d*
[Install]
WantedBy=multi-user.targetAnd while typing this lines and just doing
# systemctl disable cups.service
then
# systemctl enable cups.service
in order to post the output and reproduce the issue it suddenly worked as expected!
Offline