Tiny Core Extensions > TCE Q&A Forum
(Solved) Re: Cups can't access admin screen
aus9:
--- Quote ---I have not got to the stage of trying to actually install a printer because I haven't been able to get to an interface.
--- End quote ---
It might have helped if you had explained how your printer was connecting before?
I hope you trust me when I say, from a trouble shooting point of view, we first need to get your printer working
then and ony then do we look at how much persistence you want.
---you have already advised you print often so we will give you the works later.
Ok so you advise you have a static ip so the listen section changes but I am still unsure what you mean by hard wired?
1) ethernet cable to device, usb lead to device?
b) Do users print from the internet to this device? Or only local network users?
It looks like its similar to HP so I suggest your config becomes
--- Quote ---Listen 192.168.0.24:9100
--- End quote ---
Juanito is more of an expert than me, but I assure you, I have a hp connected to a router with a static address and assuming
Kyocera use 9100 we hope we get you to your interface.
2) do not use a /usr/local/etc/cups/client.conf unless you can't get to it.
I repeat you have a local address, if you listen to Port 631 you are listening to all ports including the net.
good luck
aus9:
ok umm lets start persistence, we will finish the /usr/local/etc/cups/ppd /usr/local/etc/cups/printers.conf only when we get an admin screen and we can only edit that admin area with root powers.
I am assuming you will print often as per reply.
1) do the root password and add the file to your backup as per info file
2) you need a PPD which will come from gutenprint and you need cups
so download gutenprint and then start apps and use the list to show the following, in addition to any other onboot stuff
--- Quote ---cups
gutenprint
--- End quote ---
A graphical way is open the apps -> maintenance -> onboot maintenance
If you accidently puts cups or dbus into ondemand please remove back to left pane ok then click into onboot and select them into right hand pane
3) Now to add persistence to 2 daemons only because you print often
edit bootlocal.sh and add the following
--- Quote ---/usr/local/etc/init.d/dbus start
/bin/sleep 3
/usr/local/etc/init.d/cups start
--- End quote ---
That sleep of 3 seconds assumes a longer boot up of 3 seconds but might stop the cups from failing.
now reboot, forget about the web page and report what you see for the following commands pls
--- Code: ---ls /usr/local/tce.installed/ | grep cups
ls /usr/local/tce.installed/ | grep dbus
/usr/local/etc/init.d/dbus status
/usr/local/etc/init.d/cups status
--- End code ---
if daemons are not falling over, then its the quality of the cups.d file to get you to the web interface
good luck
PS could you do a favour and not have any internet conf file so we are truly testing local only
ie remove /usr/local/etc/cups/client.conf if you have one from persistence and reboot etc
athouston:
Hi AUS9,
Thanks again.
from the top...
my tinycore workstation (192.168.0.22 dhcp) is connected direct to a gigabit switch by an ethernet cable.
my Kyocera FS1118mfp printer (192.168.0.24 static) is connected direct to the same gigabit switch by an ethernet cable and it uses 9100.
my internet firewall / router / modem (192.168.0.253 static) connects direct to this same gigabit switch by an ethernet cable.
All users on the internal network print from various applications, including web pages, to this network.
No-one outside of the internal network can print to the printer.
I have changed cupsd.conf to reflect listen 192.168.0.22:9100 and saved it.
I do not have a client.conf file.
usr/local/etc/cups/cupsd.conf is in the included files list of backup and I have tested this successfully.
athouston:
I download onboot gutenprint and confirm it and cups are both onboot.
The grep commands you list report -
cups
cups-filters
libcups
libcups-filters
dbus
dbus is running
cups is running
Changing the listen entry to listen 192.168.0.22:9100 did not work. I changed it back to listen localhost:9100 and I can now open the admin screen.
I have added my printer and all is now well... I can print.
The last thing to fix then is how do I make the new root password persistent please.
aus9:
good I won't ask you why did not like my suggestion earlier to use the actual static address, I promise I won't ask :D
Persistence part two
Okey dokey
Since we know a lot of people are printing here, it does make sense to have full persistence.
as per info file, add the following to your filetool.lst---we drop the first /
--- Quote ---usr/local/etc/cups/ppd/
usr/local/etc/cups/printers.conf
usr/local/etc/cups/cupsd.conf
etc/shadow
--- End quote ---
the order is not important, on reboot check the files exist pls
(b) When and if you decide to add your second printer, as I don't know what it is....(grins like a sheep) I may assume gutenprint or hplip-2.7 might supply the PPD for you.
---If you need the hplip-2.7 remember to add it as "onboot" download.
Although they supply a PPD.....they also supply a filter.....which is kind of the in between software to convert what you see on the screen into some kind of language understood by printers.
and then because you are adding a printer, you need the root password
it does not have to be the same password....but I am lazy and do keep the same one.
forgive me for sucking eggs.....choose an acronym style
Pretend you like a movie line
Give the Bag to Bozo....become GtBtB add some sqiuggles especially $ symbol and the like, add some numbers
test it works before saving
--- Code: ---sudo passwd
<new passwd> (repeat)
su tc
su
(test new password takes you to root)
--- End code ---
#####
if you do add a second printer usr/local/etc/cups/ppd/ is a folder and on reboot you will see 2 PPDs so no action by you.
--This setting was first started by Juanito is smarter than me.
some people may not like you keeping the same password....so every so often you can change it, the backup system remember the files.
good luck
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version