All,
TDE crash on start:
The big issue is that TDE crashes on start without any apparent error or anything written to .xsession-errors. After selecting the username from the chooser list in tdm and entering the password, the following occurs:
(1) login appears to proceed (2) normal black background and default X-cursor appears (3) 3-5 additional seconds of load takes place, then (4) tde crashes and tdm login re-appears.
So I look around to find out if there are any clues. None apparent. /var/tmp/kdecache-root was created, but nothing in it, then I check disk space left. WTF?? Something has taken 7.8G of room on my / partition and I have no room left on my drive?? Searching...
/var/log/tdm.log 5876092928 - WHAT? 5.8G log file??
I could not preserve the file because I had no way to compress it and git it out of my virtual machine. I'll restart and try and capture a smaller log. What in the heck could be causing tdm.log to explode like this? I know it would help to see what was inside, but that will have to wait until I can get shared folders setup and get another log out of the VM....
Anybody else ever experience this?
All,
TDE crash on start:
The big issue is that TDE crashes on start without any apparent error or anything written to .xsession-errors. After selecting the username from the chooser list in tdm and entering the password, the following occurs:
(1) login appears to proceed (2) normal black background and default X-cursor appears (3) 3-5 additional seconds of load takes place, then (4) tde crashes and tdm login re-appears.
So I look around to find out if there are any clues. None apparent. /var/tmp/kdecache-root was created, but nothing in it, then I check disk space left. WTF?? Something has taken 7.8G of room on my / partition and I have no room left on my drive?? Searching...
/var/log/tdm.log 5876092928 - WHAT? 5.8G log file??
I could not preserve the file because I had no way to compress it and git it out of my virtual machine. I'll restart and try and capture a smaller log. What in the heck could be causing tdm.log to explode like this? I know it would help to see what was inside, but that will have to wait until I can get shared folders setup and get another log out of the VM....
Anybody else ever experience this?
-- David C. Rankin, J.D.,P.E.
Not I, and this sounds pretty nasty. I'd love to have a look inside. ;-)
Tim
On Mon, Mar 5, 2012 at 8:08 PM, David C. Rankin drankinatty@suddenlinkmail.com wrote:
All,
TDE crash on start:
The big issue is that TDE crashes on start without any apparent error or anything written to .xsession-errors. After selecting the username from the chooser list in tdm and entering the password, the following occurs:
(1) login appears to proceed (2) normal black background and default X-cursor appears (3) 3-5 additional seconds of load takes place, then (4) tde crashes and tdm login re-appears.
So I look around to find out if there are any clues. None apparent. /var/tmp/kdecache-root was created, but nothing in it, then I check disk space left. WTF?? Something has taken 7.8G of room on my / partition and I have no room left on my drive?? Searching...
/var/log/tdm.log 5876092928 - WHAT? 5.8G log file??
I could not preserve the file because I had no way to compress it and git it out of my virtual machine. I'll restart and try and capture a smaller log. What in the heck could be causing tdm.log to explode like this? I know it would help to see what was inside, but that will have to wait until I can get shared folders setup and get another log out of the VM....
Anybody else ever experience this?
You could at least look at its 'tail'. Looks like someone flooded with error message in endless loop.
On 03/05/2012 10:08 AM, David C. Rankin wrote:
WTF?? Something has taken 7.8G of room on my / partition and I have no room left on my drive?? Searching...
/var/log/tdm.log 5876092928 - WHAT? 5.8G log file??
Happened again, and I stopped tdm. However, the tdm, tdm_greet, and some trinity task named 'tsak' kept running and filled the filesystem up again. So I rebooted and restarted tdm again, immediately stopped it, then tried manually killing tdm, tdm_greet and tsak. tsak stopped, but I had to kill -9 tdm and tdm_greet. I was typing fast, but still ended up with 250M tdm.log. That one I'm saving and I'll report back after I get it compressed and off the box.
On 03/05/2012 10:38 AM, David C. Rankin wrote:
On 03/05/2012 10:08 AM, David C. Rankin wrote:
WTF?? Something has taken 7.8G of room on my / partition and I have no room left on my drive?? Searching...
/var/log/tdm.log 5876092928 - WHAT? 5.8G log file??
Happened again, and I stopped tdm. However, the tdm, tdm_greet, and some trinity task named 'tsak' kept running and filled the filesystem up again. So I rebooted and restarted tdm again, immediately stopped it, then tried manually killing tdm, tdm_greet and tsak. tsak stopped, but I had to kill -9 tdm and tdm_greet. I was typing fast, but still ended up with 250M tdm.log. That one I'm saving and I'll report back after I get it compressed and off the box.
The answer is..... :
Mar 5 10:32:46 tdm_config[677] info: Cannot open master configuration file /opt/trinity/share/config/tdm/tdmdistrc
X.Org X Server 1.11.4 Release Date: 2012-01-27 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.2.2-1-ARCH x86_64 Current Operating System: Linux valkyrie 3.2.8-1-ARCH #1 SMP PREEMPT Mon Feb 27 21:51:46 CET 2012 x86_64 Kernel command line: root=/dev/disk/by-uuid/1570fb5b-7b73-4d40-a7ed-2f31bbb8b440 ro vga=0x318 Build Date: 29 January 2012 03:38:00PM
Current version of pixman: 0.24.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 5 10:32:47 2012 (==) Using config directory: "/etc/X11/xorg.conf.d" (EE) Failed to load module "vesa" (module does not exist, 0) (EE) Failed to load module "fbdev" (module does not exist, 0) (EE) AIGLX error: vboxvideo does not export required DRI extension (EE) AIGLX: reverting to software rendering (EE) VirtualBox USB Tablet: failed to initialize for relative axes. Found 1 keyboard(s) Reading from keyboard: (AT Translated Set 2 keyboard) AT Translated Set 2 keyboard+tsak Device created. Hotplug monitoring process started No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. No Device from receive_device(). An error occured. <.... snip billions more...>
<snip>
Found 1 keyboard(s) Reading from keyboard: (AT Translated Set 2 keyboard) AT Translated Set 2 keyboard+tsak Device created. Hotplug monitoring process started No Device from receive_device(). An error occured. No Device from receive_device(). An error occured.
<snip>
Interesting. I think I know where these messages are coming from (the tsak daemon), and part of the problem is that the tsak messages are somehow ending up in the tdm log.
I'm working on a fix, but I need to test it before I can push it to GIT.
Tim
<snip> > Found 1 keyboard(s) > Reading from keyboard: (AT Translated Set 2 keyboard) > AT Translated Set 2 keyboard+tsak > Device created. > Hotplug monitoring process started > No Device from receive_device(). An error occured. > No Device from receive_device(). An error occured. <snip>
Interesting. I think I know where these messages are coming from (the tsak daemon), and part of the problem is that the tsak messages are somehow ending up in the tdm log.
I'm working on a fix, but I need to test it before I can push it to GIT.
Tim
This should be fixed in GIT hash 696fe63. Please rebuild and test.
Tim
On 03/05/2012 03:05 PM, Timothy Pearson wrote:
This should be fixed in GIT hash 696fe63. Please rebuild and test.
Tim
will do and I'll report back. will take a couple of hours...
On 03/05/2012 03:05 PM, Timothy Pearson wrote:
This should be fixed in GIT hash 696fe63. Please rebuild and test.
Tim
Tim,
Confirmed fixed! Thanks. Now I have to figure out why there is no TDE session offered by tdm?? That's a packaging issue I believe :) Looks like the trinity.desktop didn't end up in the right place... (never hurts to have fluxbox installed as a backup :)
http://www.3111skyline.com/dl/dt/trinity/ss/tdm-no-session.jpg
/var/tmp/kdecache-root was created, but nothing in it, then I check disk space left. WTF?? Something has taken 7.8G of room on my / partition and I have no room left on my drive?? Searching...
/var/log/tdm.log 5876092928 - WHAT? 5.8G log file??
Anybody else ever experience this?
Not directly, but perhaps I'll file a bug report against the problem. Unlike the Xorg.0.log, tdm.log is never deleted and started fresh with each session. The tdm.log file just grows and grows and grows....
In my Slackware system I long ago modified the stock rc.4 startup script to include deleting the log file before actually starting run level 4, which for Slackware is the graphical login. A more appropriate solution is TDM or TDE performing its own house keeping.
With that said, unless this log file has been growing for a very long time and you did not notice the ever shrinking file space, to grow to a GB size means a runaway loop of some kind. I would test methodically. That is, reboot and before starting graphical mode, ensure the log file is always deleted.
If your operating system allows a spare console for command line logins even when in graphical mode (in Slackware console number 6 is excluded from graphical logins), use that console to login and monitor the tdm.log file with tail. If there is no available console, use ssh to monitor the log file.
Side note: sounds as though your /var file system is on the same partition as your root file system. Placing /var on its own partition would have avoided any lock up due to file space because only that partition would have filled and not your root system. Placing /var on a separate partition is common practice and now you have real world experience why that practice started. :)
Darrell
-
Aleksey Midenkov -
Darrell Anderson -
David C. Rankin -
Timothy Pearson