Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
For that matter, how much physical memory is in the machine?
re - mail:
Typically this would show you the local mailboxes, if any.
Code:
ls -a /var/spool/mail
but you might be able to double check the location with the command
Code:
echo $MAIL
to see to what directory it points.
re - ports:
Generally, cupsd wants to control port 631 at least. Do you have a firewall in place? Some such facilities can be used to prevent inside access. Although often the main focus would be to prevent outside access. But you might want to double check. Do you have iptables or eptables installed, or any sort of firewall software?
re - upgrading:
I don't see any mention in the release notes that cups now installs, if that's what you mean by a reason for upgrading. When I upgrade, if possible, I usually try to arrange things to that I can multi-boot, the old release side by side with the new release, in case there is anything wrong with the new release, and I decide I want to keep running the old. Or just in case I want to double check the way things worked in the old release, I can boot the old release.
:~# ls -a /var/spool/mail
ls: /var/spool/mail: No such file or directory
~# echo $MAIL
/var/mail/Peters
:~# cd /var/mail/Peters
sh: cd: can't cd to /var/mail/Peters
:~# ls -l /var/spool/Peters
ls: /var/spool/Peters: No such file or directory
Code:
:~# iptables
sh: iptables: not found
:~# eptables
sh: eptables: not found
Any other way to check if I have a Firewall installed?
Upgrade:
Ummm. Only to perhaps cure the problem? Though no one else has (so far) commented about install problems with cups with V2.0
If I can find time today I'll try V3.0 on another clean hard drive.
Last edited by fopetesl; 03-31-2010 at 03:53 AM.
Reason: Bad info
For ulimit, the remaining value I believe usually uses the d flag, as in:
Code:
ulimit -d unlimited
If you could get to the point where all the memory related items say unlimited, and then try starting cupsd, that would be nice.
Also, how much physical memory is on the machine?
The MAIL variable points to what can be a mail file if there is local mail for a particular User.
What you'd want to do as root is something like this to look at what else might be in that directory:
Code:
ls -al /var/mail
I saw a mention of mail in the trace files, and I wondered if maybe the cupsd might have mailed root, or some "system" user locally. If it had, the mail might be in that directory.
Sure, installing the new version of the OS might be worth a shot.
As to the firewall, the only things I know of on the list of packages for that distro that might implement a firewall are the *tables stuff.
Can you get a list of all packages you have installed so we could check if there might be something else that has the port closed?
# tail /var/log/messages
Mar 31 10:30:58 (none) user.info kernel: cupsd[1314]: segfault at 0 ip (null) sp bff67660 error 4 in cupsd[40000000+52000]
__and an old
Code:
# cat /var/log/cups/error_log
E [27/Mar/2010:11:35:54 +0000] Hostname lookup for "hostname" failed!
E [27/Mar/2010:11:35:54 +0000] Bad Listen address hostname:80 at line 17.
but it's a few days old and we've tried running cupsd several times since then
I had a look into /etc/cups/cups.conf to (re)checl the "Listen" ports:
Thanks. This new information opens a variety of possibilities.
You realize of course, that if this problem gets solved, you could potentially write the much needed manual on installing cups in the distro!
OK, so it doesn't appear to be a memory problem.
The install log looks a bit inconsistent. It almost looks as though it let you install cups when cups was already installed and produced different results, for different re-installs. It seems unknown as to whether or not it should consider cups to be installed properly, the way it seems to, even though cupsd won't start. Also, are those all the that packages that are installed, or just packages that have been installed recently?
So you are saying that when you try to run cupsd currently, you don't get any current log messages about the hostname lookup problem, is that right? Your machine has a host name within Linux with an associated IP address, even if it's a default host name and IP address, right? For example, if you run the command:
Code:
hostname
you get some name displayed. Then if you take the name displayed by the hostname command, say for example the name is linux which is a default on some distros, and you then use the grep command to look for that host name in your /etc/hosts file, for example:
Code:
grep linux /etc/hosts
you'll find an ip address in /etc/hosts associated with whatever host name the hostname command outputs, yes?
Would you please try to attach the cups config file and log files to this thread.
You realize of course, that if this problem gets solved, you could potentially write the much needed manual on installing cups in the distro!
Like I have time. Already.
But if we get it up and running I'll find the time!
The install log seems to be complete though I have no way to be 100% certain. It does include the programs that Slitaz installed automagically when installing to HDD initially so probably true.
The multiple installs of cups were varieties of install-from-cache, remove-then-reinstall and clean-the-download-cache-and-do-a-fresh-install. The busybox "(re)install"s were a response to "do you want to repair/reinstall programs modified by cups install?".
So I added the line to /etc/hosts: 127.0.0.1 localhost Peters.
Well, that didn't work!
Code:
root@Peters:/etc# /etc/init.d/cupsd start
Starting cups deamon: Cupsd... cupsd: Child exited on signal 11!
[ Failed ]
Umm. Sorry. Which log file(s) do you want to see?
/var/log/cups/error.log hasn't been updated since 27 March.
/var/log/messages has only the same as previously - cupsd segfault.
as to the log files I was just trying to double check that it was no definitely no longer complaining about hostname.
OK, I think it's time to focus on the version of the distro you're using.
When you started this thread you referred to SLITAZ cooker. So you are using the latest "cooking" version of 2.x, not the latest stable version of 2.x - is that right? What "flavor" are you using? Another to put that is, what were the names of the ISO's you installed? Or how did you go about the installation?
When you started this thread you referred to SLITAZ cooker. So you are using the latest "cooking" version of 2.x, not the latest stable version of 2.x - is that right? What "flavor" are you using? Another to put that is, what were the names of the ISO's you installed? Or how did you go about the installation?
I have it loaded on my BIG computer as Slitaz-cooking-firefox.iso.
However. Please note my earlier comment about trying Slitaz-V3.0-stable.
Nice idea but the logic doesn't hold up for distro specific. Other people have complained only of specific printer problems so maybe it's a hardware issue? - printer is plugged in and switched on though I cannot see why this may be significant.
Previously other distros, mostly Ubuntu, load cups without a printer connected and either prompt at the GUI or install through localhost:631.
Installation was via the LIVE interface since there doesn't seem to be an alternative.
Also I had to wipe the disk and create an ext3 partition (of the whole HDD) for installation, i.e. the partition has to exist or Slitaz won't install. Same for V3.0 BTW.
Actually I note on the Slitaz downloads page http://www.slitaz.org/en/get/index.html#stable (stable & cooking are all on the same page) that there are non-LIVE iso images. Should I try one of these I wonder.
Distro specific? Ummm....
[...]
I have it loaded on my BIG computer as Slitaz-cooking-firefox.iso.
However. Please note my earlier comment about trying Slitaz-V3.0-stable.
Nice idea but the logic doesn't hold up for distro specific. Other people have complained only of specific printer problems so maybe it's a hardware issue? - printer is plugged in and switched on though I cannot see why this may be significant.
Previously other distros, mostly Ubuntu, load cups without a printer connected and either prompt at the GUI or install through localhost:631.
Installation was via the LIVE interface since there doesn't seem to be an alternative. Also I had to wipe the disk and create an ext3 partition (of the whole HDD) for installation, i.e. the partition has to exist or Slitaz won't install. Same for V3.0 BTW.
Actually I note on the Slitaz downloads page http://www.slitaz.org/en/get/index.html#stable (stable & cooking are all on the same page) that there are non-LIVE iso images. Should I try one of these I wonder.
Actually, I wasn't thinking it was a problem with SLITAZ specifically. I was wondering if it was a problem with a 2.x "cooking"/un-stable version versus the 2.x stable version. Also, there are supposedly different "flavors" of SLITAZ. Even though they don't seem to make it easy on the SLITAZ site to get older releases once the new release is out, some of the mirrors have archived older versions. Also, when I downloaded the 2.0 packages ISO from ibiblio the MD5 sum was wrong. There could be something wrong with the ISO, or they might just have put up the wrong MD5 sum. I wondered if the md5sum was correct for what you had. I also wondered if you had a "cooking" version of 2.x I was going to suggest you try the latest stable version of 2.x from a mirror, one with a valid md5sum.
I have just completed a test using an older mobo, a Gigabyte G-8 board with 256MB SDRAM and Radeon AGP card. Same HDD.
cups loads and runs with no error!
And. I can connect using localhost:631.
Howto dig out THIS problem?
Could not get internet - ifconfig shows only eth2 but will not get a dhcp lease. So no more info.
Ubuntu versions load cups OK on this board with both 5.10 (Breezy) and 9.10 (Karmic) without a problem.
I see that there is a later version of cups 1.4.3 instead of this version 1.4.2.
Safe to download and (how to?) compile?
OH! I missed the latest installment when I responded. Cool! And, Freakie! Cups having problems with a motherboard?
It was my understanding that the SLITAZ folks changed a lot of things to keep the system very very very small. I wasn't sure if you were using a SLITAZ modified cups that might have other requirements like that the printer be connected so it could try to configure the printer driver, or what. Since what seemed the most likely source of the problem didn't seem to help, I was just trying look at anything, however unlikely.
As to the new cups, if the problem with cups seems like it was something with the motherboard, it might worth it to try the newer version. You could also go back to the one that works if the new one doesn't. I can't comment on the newest cups specifically, because I'm still using 1.3. I've also never had to compile cups.
As to eth2, I take it that eth2 is the interface you want to use, it's up and running, properly configured, all the proper routing is set up. Do you know if it's even sending out packets? I usually keep an old true hub around, not a LAN switch, that I can connect to a machine when I'm troubleshooting network issues. That way I can use another machine to eavesdrop on the conversations of the computer under test. Do you have lights on the NIC that will tell you whether or not it's trying to send packets? Or something you can connect to check?
The eth2 problem isn't. Yet.
For some reason ifconfig didn't show either eth0 or eth1 on the 'old' mobo, only eth2. And dummy0, local, etc.
And although I set it up to dhcp at boot which seemed to work I couldn't ping or connect.
Seems that Slitaz doesn't fully recognise eth2
However, next step.
Downloaded and tar'red cups 1.4.3.
./config throws a wobbly. Has me baffled .. see the log file.
Doesn't look like depends are missing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.