Topic: cups with 7.1

[sparticus]

Yesterday everything got updated nicely with yum to 7.1 but for some reason today everything has gone up the wall when it comes to printing. Basically, none of the networked pc's show up the printers and i cant show up cups through the server-manager or directly through ip.
I tried uninstalling cups and then re-installing it again but the exactly same problem occured.
Anybody have any suggestions?

[EdelingF]

I did a update also from 7.0 to 7.1 and had no problem. Didn't you get any errors?
I'm not that experienced, but it looks like Samba is the problem.

Freek

[sparticus]

Im not that experienced either so im not sure if Ive missed something, but I dont seem to be getting any errors myself. Thats the strange thing...
Any suggestions for any obvious places to look?

[cactus]

Im not that experienced either so im not sure if Ive missed something, but I dont seem to be getting any errors myself. Thats the strange thing...
Any suggestions for any obvious places to look?

Are you sure the upgrade did not (re-)install e-smith-LPRng, as this should be uninstalled for cups to run properly if I remember correctly.

[sparticus]

i checked that when i re-installed cups but it didnt re-install it.
Any other ideas?

[jahlewis]

Are you seeing anything in your log files that may give a clue to what is happening?

[Robert]

The installation instructions for CUPS on SME 7.0 do not work on SME 7.1 due to yum configuration changes. Apologies for not noticing this sooner. I hope to come up with a solution soonish.

[sparticus]

if you login via ssh and then do this on a clean install of 7.1 it will work with cups:

[root@hostname ~]# yum remove e-smith-LPRng

[root@hostname ~]# wget http://mirror.contribs.org/smeserver/contribs/rvandenaker/testing/smeserver-cups/repositories/7.0/RPMS/noarch/smeserver-cups-0.0.1-02.noarch.rpm

[root@hostname ~]# yum localinstall smeserver-cups-0.0.1-02.noarch.rpm

[root@hostname ~]# /sbin/e-smith/signal-event post-upgrade

[root@hostname ~]# /sbin/e-smith/signal-event reboot

Login to server manager and you can access the cups manager from there.

Cheers.

[TeNeCo]

Hello Sparticus,

sorry, but another newbie here...

>Login to server manager and you can access the cups manager from there.

then I get:

The requested URL /server-manager//cgi-bin/printers was not found on this server.

[gtob]

>Login to server manager and you can access the cups manager from there.

then I get:

The requested URL /server-manager//cgi-bin/printers was not found on this server.

Me too - Sparticus please help

[william_syd]

This was with SME 7.1.1.

Code: [Select]

wget http://mirror.contribs.org/smeserver/contribs/rvandenaker/testing/smeserver-cups/repositories/7.0/RPMS/noarch/smeserver-cups-0.0.1-02.noarch.rpm

Code: [Select]

yum localinstall smeserver-cups-0.0.1-02.noarch.rpm --enablerepo=*

Code: [Select]

signal-event post-upgrade; signal-event reboot

Code: [Select]

db configuration setprop cupsd TCPPort 631 access public

Code: [Select]

signal-event remoteaccess-update

[gtob]

This did the trick - thanks  

[cactus]

Code: [Select]

yum localinstall smeserver-cups-0.0.1-02.noarch.rpm --enablerepo=*

Be aware that enabling all repositories is not advised, users could have all kind of repositories available if their system is not an out-of-the-box installation.

Code: [Select]

db configuration setprop cupsd TCPPort 631 access public

Do you really need the port to be public? IMHO private should also do (only for local networks and external networks defined in the remote access panel), setting to public would mean the port is opened for everyone on the external interface.

[william_syd]

Code: [Select]

yum localinstall smeserver-cups-0.0.1-02.noarch.rpm --enablerepo=*

Be aware that enabling all repositories is not advised, users could have all kind of repositories available if their system is not an out-of-the-box installation.

I was lazy.

Code: [Select]

db configuration setprop cupsd TCPPort 631 access public

Do you really need the port to be public? IMHO private should also do (only for local networks and external networks defined in the remote access panel), setting to public would mean the port is opened for everyone on the external interface.

I should have stated that I run SMEserver in server-only mode and as such access from the big bad internet is controlled by another box.

However, I would think that the rpm should be setting the TCPPort property.

[gtob]

Be aware that enabling all repositories is not advised, users could have all kind of repositories available if their system is not an out-of-the-box installation.

What repositorie should you use then?