Linux Help
guides forums blogs
Home Desktops Distributions ISO Images Logos Newbies Reviews Software Support & Resources Linuxhelp Wiki

Welcome Guest ( Log In | Register )



Advanced DNS Management
New ZoneEdit. New Managment.

FREE DNS Is Back

Sign Up Now
> Remote printing problem becomes total system meltdown, Can't even login
jamespetts
post Feb 11 2009, 05:54 PM
Post #1


Whats this Lie-nix Thing?
*

Group: Members
Posts: 6
Joined: 6-August 04
Member No.: 3,497



At home, there are four computers: study, bedroom, kitchen and parlour. Kitchen and parlour are running Ubuntu Intrepid; bedroom is running Ubuntu Hardy and Study is running Windows XP.

Earlier this evening, a problem was found printing from kitchen to parlour. I had earlier configured cups using the GUI to print from kitchen to parlour without difficulty, so found this odd. I spent a great deal of time trying to solve the problem without success, the problem always appearing to be that the server was refusing permission to access it to the clients, even though the server was configured to allow remote printing and remote administration, the clients' IPs were in the allowed list, all relevant usernames were given permission to print, and it had worked with those exact settings recently before.

I tried to configure the printer from bedroom (I had not previously set up the printer from there), and got exactly the same error. I tried to access the CUPS web configuration on parlour, from bedroom and I got a 403 (I had earlier tried the same from kitchen with the same result). So, on bedroom, I tried to configure the printer through Bedroom's CUPS web interface. I added a printer, and selected the appropriate driver (HP Photosmart D7300 series). I sent it a test page from the web interface, but nothing printed - it was marked perpetually as "processing".

I went to parlour to investigate, and could now not access the CUPS web interface even locally - it appeared that the web server was not giving any sort of response. I tried restarting CUPS from the command line, but got a segmentation fault. Trying to reboot from the command line also gave a segmentation fault. I rebooted from the GUI. The loading bar screen appeared, but there were bizarre artefacts (looking like fragments of the blank loading bar under the Ubuntu logo) next to the live loading bar, which progressed as normal.

I reached the login screen as normal, but any attempt to login just brought the interface back to the login screen again, even with "failsafe terminal" selected as the session. I tried rebooting in failsafe mode from the GRUB menu, and attempted to use the automatic repair tools there (FSCK, XFIX, and DPKG fix), but, on rebooting again, there was no change. I am at a total loss, and very concerned that something quite drastic but utterly incomprehensible has gone wrong. I cannot even access shared NFS folders on parlour from other computers. I should be very, very grateful for any assistance at all, especially as this is my parents' computer that I help to maintain for them and they really do rely on it for a great many things.
Go to the top of the page
 
+Quote Post
 
Start new topic
Replies
michaelk
post Feb 13 2009, 12:25 PM
Post #2


Its GNU/Linuxhelp.net
*******

Group: Support Specialist
Posts: 1,797
Joined: 23-January 03
Member No.: 360



sr0 and sr1 are your CDROM drives. The errors posted are from sr0 which I assume is the live CD.
How many hard drives are attached including removable USB etc.
Go to the top of the page
 
+Quote Post
jamespetts
post Feb 15 2009, 04:03 PM
Post #3


Whats this Lie-nix Thing?
*

Group: Members
Posts: 6
Joined: 6-August 04
Member No.: 3,497



QUOTE (michaelk @ Feb 13 2009, 12:25 PM) *
sr0 and sr1 are your CDROM drives. The errors posted are from sr0 which I assume is the live CD.
How many hard drives are attached including removable USB etc.


Thank you very much for your reply :-) Yes, I suspected that sr0 is a CD; I am not sure where that gets me, if anywhere. There is only one local hard drive in the system: other are setup to be mounted via NFS or SAMBA, but I don't think that that's what you meant, is it? There are two optical drives and one old-fashioned floppy drive, too, all IDE (either old-fashioned ribbon cable IDE for the optical drives, or SATA (but running through a third party bridge chip onto the motherboard's PATA port) for the hard drive).

This problem seems to be login-specific: even when I try CTRL+ALT+F1 at the login screen, I get a text login which, when a valid username and password pair are entered, simply re-prints the text login again. Entering an invalid username/password pair gives the correct "login incorrect" response, so the system can discriminate between valid and invalid pairs: it is not a simple case of loss of username/password data. I suspect that a similar problem might have precipitated the inability to print remotely (the system companied that authorisation was denied), and even problems with remote backups (authorisation problems again seemed to be the cause), but what would cause the whole login system to fail completely? And why the sudden segfaults when trying even to reboot? This is all very mysterious.
Go to the top of the page
 
+Quote Post

Posts in this topic


Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 20th October 2017 - 12:47 PM