Pete Connolly wrote:

On Wednesday 25 Feb 2009 16:19:09 Kai Ponte wrote:

...

On my son's laptop, I went to reboot this morning. (I was trying to see why I couldn't connect via ssh.) On boot, I got a message that /tmp was full and that the desktop manager would not start.

What do I do? It won't let me login.

Hi Kai

I'd boot from the opensuse disk, skip the install then mount your partitions and clear out /tmp.

Further on this, there's a setting in sysconfig that will clear /tmp on reboot or after a specified time. -- Use OpenOffice.org <http://www.openoffice.org> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Boris Epstein wrote:

Boot the "failsafe" mode, or, failing that, boot from a CD/DVD and select the "rescue" system. Then locate the /tmp partition and clean it up.

Boris.

Okay, will do. What do I click on in failsafe mode to locate it? Do i log in as root there? -- kai ponte www.perfectreign.com || www.filesite.org XCJNaWNyb3NvZnQgaXNuXCd0IGV2aWwsIHRo ZXkganVzdCBtYWtlIHJlYWxseSBjcmFwcHkg b3BlcmF0aW5nIHN5c3RlbXMuXCIgLSBMaW51 cyBUb3J2YWxkcw== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Kai Ponte wrote:

Boris Epstein wrote:

...

On Wed, Feb 25, 2009 at 11:19 AM, Kai Ponte <opensuse@perfectreign.com> wrote:

...

On my son's laptop, I went to reboot this morning. (I was trying to see why I couldn't connect via ssh.) On boot, I got a message that /tmp was full and that the desktop manager would not start.

What do I do? It won't let me login.

-- kai ponte www.perfectreign.com || www.filesite.org

XCJNaWNyb3NvZnQgaXNuXCd0IGV2aWwsIHRo ZXkganVzdCBtYWtlIHJlYWxseSBjcmFwcHkg b3BlcmF0aW5nIHN5c3RlbXMuXCIgLSBMaW51 cyBUb3J2YWxkcw==

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Boot the "failsafe" mode, or, failing that, boot from a CD/DVD and select the "rescue" system. Then locate the /tmp partition and clean it up.

Boris.

Okay, this seems to be a little more of an issue. I deleted - as root - all files in /tmp /usr/tmp /var/tmp

On boot, after selecting which user to login with, I get the message, "Call to lnusertemp failed (temporary directories full?). Check your installation."

I had a chat with my friend, google, and I found and followed directions here:

http://bbs.archlinux.org/viewtopic.php?id=43335

http://www.kde-forum.org/artikel/17997/call-to-lnusertemp-failed-temporary-d...

http://www.pclinuxos.com/index.php?option=com_smf&Itemid=26&topic=23065.0;wap2

http://www.linuxquestions.org/questions/mandriva-30/call-to-lnusertemp-faile...

So far, no luck.

I can login as a user either on console or another Window manager - IceWM but not GNOME or KDE.

Ideas?

Rename the .kde and .kde4 dirs. in your /home/? dir. with something like a .org extension. Then try to login. If it works, just setup KDE again, and delete the 2 .kde.org dirs. Fred -- "The fundamental premise of liberalism is the moral incapacity of the American people." ~ Alan Keyes -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

if /tmp is on / (which is the default) you might be better off to clear some excess data from somewhere else on the partition. On Wed, Feb 25, 2009 at 11:36, Carl Hartung <suselinux@cehartung.com> wrote:

On Wednesday 25 February 2009 11:19:09 Kai Ponte wrote:

...

On my son's laptop, I went to reboot this morning. (I was trying to see why I couldn't connect via ssh.)  On boot, I got a message that /tmp was full and that the desktop manager would not start.

What do I do? It won't let me login.

Hi Kai,

Boot into rescue mode using an install CD or DVD.

The default login is 'root' with no password.

Mount the partition with /tmp and /var/tmp (usually '/')

Clear out both directories (i.e. 'cd /tmp' then 'rm -rf *' etc.)

umount '/' and 'init 6' to reboot

Once booted into desktop, launch YaST's "/etc/sysconfig Editor"

Drill down to 'System' -> 'Cron' -> 'TMP_DIRS_TO_CLEAR'

Add to settings: "/tmp /var/tmp" (no quotes)

Then go to 'System' -> 'Cron' -> 'CLEAR_TMP_DIRS_AT_BOOTUP'

Set to "yes" (no quotes)

This problem will not recur.

hth & regards,

Carl

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-02-25 at 13:48 -0300, Cristian Rodríguez wrote:

remove stuff from /tmp then install package tmpwatch to avoid this in the future.

Could you expand on that tmpwatch, instead of using the traditional suse cron job that deletes old tmp files? This is new to me. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmlskgACgkQtTMYHG2NR9VgYgCfePjin+vecD5tcM0Qeze072x8 oa8An0zpJyJAFu7uYVQPUHnm2fRVh7Er =R19X -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-02-25 at 18:22 -0300, Cristian Rodríguez wrote:

Carlos E. R. escribió:

...

Could you expand on that tmpwatch

see man 8 tmpwatch :)

I don't have it installed, I can't look the manual. And the manual probably will not explain whether or why it is better than the traditional suse cron job :-)

instead of using the traditional suse

...

cron job that deletes old tmp files? This is new to me.

tmpwatch also installs a daily cronjob that takes care of the task, it is new to you because tmpwatch reappeared in the distribution only in 11.1.

Ah, then it is not in use in 11.0. And my test partition of 11.1 doesn't have it, either, so it is not installed by default.

ps: note that there are several utilities with that name, we use the one maintained by redhat https://fedorahosted.org/tmpwatch/

There is one for 11.0, but I don't know if it is that one: cer@nimrodel:~> webpin tmpwatch 5 results (3 packages) found for "tmpwatch" in openSUSE_110 * tmpwatch: Watches file system activity, such as /tmp files - 2.9.13 [suse-oss | BS::home:/elvigia] - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmmBXYACgkQtTMYHG2NR9VAWwCbBgHL5z+r2DrEmL3afctcDUoD rU0AnR9H4ejUZn6Qq0+kFETiUlQkZwq2 =Wc3W -----END PGP SIGNATURE-----

Carlos E. R. wrote:

...

see man 8 tmpwatch :)

I don't have it installed, I can't look the manual.

I guess "see man 8 tmpwatch" is shorthand for "type 'man 8 tmpwatch' into google (without the ')" :) Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2009-02-28 at 11:02 +0100, Peter Ragosch wrote:

Hi Kai,

I've just running in a similar problem: couldn't log into kde desktop.

I could solve the problem by deleting (as root on init 3 level) /var/log/zypper.logxxxx A log file with more then 23 GB! eating up all HD space.

Now every think works fine again.

Hope that helps.

Did you look inside that log file, to see what was taking so much space? Someone having this problem has to look and fill a bugzilla. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmpNtcACgkQtTMYHG2NR9UxCACfbaj6DMGpTBiZilgcnuAxBy33 wswAnRf57FErX0ZzdkOUJYrBw/t/nQBO =D0zN -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Saturday 28 February 2009 16:36:59 Rajko M. wrote:

I looked zypper logs and they all are 6.5 MB since openSUSE 11.1 installation. It could be that enormous logs are result of mixed updates and factory usage. One can expect that default debug level of factory packages is elevated to give more details.

/etc/logrotate.d/zypper.lr says it will rotate a file once it hits 10MB, and it will keep 99 old versions. This should mean a max of 1GB (10MB*100) for all of them, but if something happens in the space of one day, to make one of the log files spin out of control and become several gigabytes in size, logrotate won't handle it, since it only runs once per day It would be interesting to know what is in those very large log files. There must be something wrong somewhere Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Rajko M. a écrit :

I looked zypper logs and they all are 6.5 MB since openSUSE 11.1 installation. It could be that enormous logs are result of mixed updates and factory usage. One can expect that default debug level of factory packages is elevated to give more details.

I just looked at my fresh 11.2 factory install, done by installing first 11.1 then switching repos to 11.2, zypper.log is just 5.8Mo jdd -- http://www.dodin.net http://valerie.dodin.org http://www.youtube.com/watch?v=t-eic8MSSfM http://www.facebook.com/profile.php?id=1412160445 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Saturday 28 February 2009 20:10:43 Fred A. Miller wrote:

What's nasty is that if you setup your system to delete everything in /tmp on bootup, then the system takes forever to finally get to a login prompt, so that's not a solution either.

It wouldn't have much of an effect on things under /var/log, certainly. The solution here is to find out why zypper starts logging so much on those systems, and to do that, we need to know what is actually in those log files Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 03/01/2009 03:14 AM, Anders Johansson wrote:

The solution here is to find out why zypper starts logging so much on those systems, and to do that, we need to know what is actually in those log files

Which is also a kind of catch 22, since it is too big to send, and no more room to add any files. I have had it happen once here, and the goal in the "panic" is to get some room to keep the whole system from crashing because of no more room on /, secondarily to figure out why (but also impossible because though now your system is working OK again, the huge log file is deleted. It seems to be an anomaly, since it hasn't happened since here, so it would probably be very difficult to fix anyway. My guess is download errors from a bad repository, or who knows. -- Joe Morris Registered Linux user 231871 running openSUSE 11.1 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

jdd wrote:

,,, root have reserved area, normally to avoid such problem and always allow root login. but I beg if it's a root app that crashes and fills the disk, this don't work. ...

Why hasn't anyone yet advised the OP to put /tmp and /var onto a separate, dedicated partition? That would solve the whole problem without all these struggles. I can't remember where I got that advice from --wasn't it on this list several years ago? John Perry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

John E. Perry schreef:

jdd wrote:

...

,,, root have reserved area, normally to avoid such problem and always allow root login. but I beg if it's a root app that crashes and fills the disk, this don't work. ...

Why hasn't anyone yet advised the OP to put /tmp and /var onto a separate, dedicated partition? That would solve the whole problem without all these struggles.

I can't remember where I got that advice from --wasn't it on this list several years ago?

John Perry

When the thread started, it wasn't yet known that /tmp wasn't the problem but /var. Putting /tmp separate wouldn't have solved the problem, there would still have been other issues. If RAM is big enough, it may be a good idea to mount /tmp as tmpfs. It's not always suitable but it works for me. Putting /var separate may sound like a nice idea, but in my really humble opinion it is overkill except when you run a server. For a desktop machine, it's really not necessary to put /var separate. The problem discussed in this thread was probably just a fluke. To make good use of a lot of partitions, you'd have to use LVM, because else you would always have that problem that you allocated too much or too little space to a partition. -- Amedee -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

John E. Perry wrote:

jdd wrote:

...

,,, root have reserved area, normally to avoid such problem and always allow root login. but I beg if it's a root app that crashes and fills the disk, this don't work. ...

Why hasn't anyone yet advised the OP to put /tmp and /var onto a separate, dedicated partition? That would solve the whole problem without all these struggles.

I'd suggest that telling the OP (me) to do such a thing - after installing the system using the 11.1 installer - would be folly. If the installer had wanted me to do this it would have told me so. Remember, I'm an average user who just want a system that works, and I prefer not to downgrade to the commandline unless I have to. -- kai www.perfectreign.com | www.ecmplace.com www.twitter.com/PerfectReign -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

James Knott wrote:

Fred A. Miller wrote:

...

What's nasty is that if you setup your system to delete everything in /tmp on bootup, then the system takes forever to finally get to a login prompt, so that's not a solution either.

Fred

Actually, you can configure cron jobs to clear out old stuff in /tmp. That cuts down on that which has to be deleted at boot.

NADA....that isn't what happens, as I pointed out. I've ALWAYS setup cron to do just that....clean it out on boot, but with EVERY system I've tried that on, 32- and 64-bit with KDE4.*, the system CRAWLS during boot AND logon. This was never the case with 11.0 and earlier releases. Now, what I don't know, as I don't have any boxen setup anywhere with 11.1 and KDE3.5, is if KDE4.* is causing this or not. Fred -- The problem with socialism is that you eventually run out of other people's money. - Margaret Thatcher -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Fred A. Miller schreef:

James Knott wrote:

...

Fred A. Miller wrote:

...

What's nasty is that if you setup your system to delete everything in /tmp on bootup, then the system takes forever to finally get to a login prompt, so that's not a solution either.

Fred

Actually, you can configure cron jobs to clear out old stuff in /tmp. That cuts down on that which has to be deleted at boot.

NADA....that isn't what happens, as I pointed out. I've ALWAYS setup cron to do just that....clean it out on boot, but with EVERY system I've tried that on, 32- and 64-bit with KDE4.*, the system CRAWLS during boot AND logon. This was never the case with 11.0 and earlier releases. Now, what I don't know, as I don't have any boxen setup anywhere with 11.1 and KDE3.5, is if KDE4.* is causing this or not.

Fred

That must be a OpenSuse+KDE4.* issue, because I don't have that experience with Ubuntu+KDE4 or Gentoo+KDE4. Anyway, I can't imagine why KDE4.* would be responsible for a slow _boot_. Logon perhaps, but boot??? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Peter Ragosch wrote:

Am Wed, 25 Feb 2009 08:19:09 -0800 schrieb Kai Ponte <opensuse@perfectreign.com>:

...

On my son's laptop, I went to reboot this morning. (I was trying to see why I couldn't connect via ssh.) On boot, I got a message that /tmp was full and that the desktop manager would not start.

What do I do? It won't let me login.

I've just running in a similar problem: couldn't log into kde desktop.

I could solve the problem by deleting (as root on init 3 level) /var/log/zypper.logxxxx A log file with more then 23 GB! eating up all HD space.

Now every think works fine again.

Hope that helps. Peter

That was the file that did it for me. Mine was way bigger than I expected. His machine has been running fine ever since. -- kai www.perfectreign.com | www.ecmplace.com www.twitter.com/PerfectReign -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org