My system just shut itself down as I was using it. I'd like to try to understand why.
First, I noticed there are 1 to 4 messages per second in my messages.1 through messages.4 files in /var/log going back to September 27. It probably started before then, but I don't have older logs.
There almost nothing else in the messages log but these messages, millions of them. They look like these:
Quote:
Then just before shutdown, there are a few dozens of these:
Quote:
And then right at the end, a switch to runlevel 0. I did not initiate that. Something else did. And finally a dbus-daemon segfault.
Offlate I installed F11 i586 on my laptop. F11 shares the hard disk with Vista Home Premium 32-bit. The problem is that when running F11 (or even Ubuntu), my system shut off suddenly(not a normal OS shut down, but a sudden power off without any warning). This could have been a hardware trouble(heating) but it doesn't happen with Vista. Machine specifications: Maker: Toshiba Model: Satellite L305D-S5881 AMD Turion X2 Dual Core Mobile Processor RM-70 3072 MB 800 MHz SDRAM I don't want to open up my machine unnecessarily, if it isn't a hardware issue. I am not sure how to verify the bit length of the machine and the OS and does it create a compatibility issue ? Your advise would be highly appreciated.
I am experiencing an issue with the system shut down. Everything works fine, but the system is not able to automatically power off and I have to manually switch it off. How could I fix this behavior?
I just installed 11.3 and Gnome yesterday and all went well except that the system will not shut down, it simply reboots. I've tried shutting it down using halt and shutdown now as root and each time the machine reboots. I didn't have this problem with 11.1.
I am using lenny on an Intel 5200 dual core machine with 2 GB RAM
The problem facing is sometimes The dialog box "The sustem will immediately shut down" is shown and goes to power off. I thinks it is connected with a hardware problem. But It is difficult to trace out what is the problem and in which part of the hardware it is.
The motherboard of this computer was complaint and it was replaced by the company (It is seen than it is the same motherboard with one IC replaced)
The problem is difficult to identify since it is not happening every time. When the service persons are here it is working fine. But when i works with the computer seriously, the problem arises - mostly in night. I have checked the power, voltage etc - everything fine. Also it is in linux, service persons don't pay attentions to solve the problem.
Is it the problem with RAM? It is a new RAM. Even if it is bad I can't replace it because it is working! and in windows (service persons check it with windows only)
I have an online server which I can not reach any more !
Code:
normally works just fine but now there is a timeout...
Code:
Status of csf:csf and lfd have been disabled, use 'csf -e' to enable Status of lfd:lfd is stopped. The only thing I have is a management-interface with a command prompt(luckily !) You can see that any firewall is disabled.
Still I can not reach my server. Not through webmin via the public address, not through the VPN on the private address (10.10.0.1). So no webmin. I cannot reach my server via ssh. I cannot ping my server on the public IP-address from my client.
What else besides the firewall can restrict my access to my server ?
So I've got a backup server that has a daily cronjob to back up all my systems. My desktop PC is usually in sleep mode to save power. So my backup server has to wake up the desktop via wake-on-LAN to start the backup job. When the backup script is done, my backup server sends a shutdown command to the desktop to put it back in sleep mode.
The trouble is that SSH is timing out during the shutdown process and waits a ridiculous amount of time before giving up and allowing my backup server to move on to the next backup script. Here's the portion of my backup script for the desktop that does the shutdown stuff:
Code: ssh user@host.lan '/usr/bin/shutdown -p +1'
Here's what cron sends me via e-mail:
Code: Read from remote host host.lan: Connection timed out real 164m46.280s user 5m16.160s sys 1m39.760s
Normally the entire backup job will only take about 5 minutes. But because of SSH timing out, it takes 164 minutes!
As a matter of detail, my backup server is running Ubuntu 9.10, and the desktop is Windows 7 x64 with Cygwin. The -p option for the shutdown command in Cygwin is for sleep mode.
I am using Ubuntu 9.04. Years ago, I did UNIX and DOS line commands, but I am 66 and dim, though my doctor says he still thinks I have my marble.Anyway, my Linux shuts down automatically faster than I want it to.How does one control this?
If I click on the shutdown bottom (in my lower panel) I get an new window to choose if I really want to shut down or restart or suspend or hibernate. Under that alternatives there is an text that says: "[...] The system will automatically shut down in 60 seconds." Why is the text "60" not running down like a countdown? Can I set another (shorter) time for the automatic shutdown (10 seconds)? If so, where? Or shut I just make another bottom to shut down immediately?
I use (normally) OpenSuse/SUSE Linux Release 11.1 Kernel Linux 2.6.27.45-0.1-pae Gnome 2.24.1
I want to know the exact command to shut down a red hat linux server.I was using init 0. but some one said its not the proper method to shut down my linux server.If not which is the exact command
Using the ubuntu live cd 9.10 I get weird error messages when shutting down the system, sometimes it is this one: device removed: /freedesktop/Hal/devices/net_80_00_60_0f_e8_00
Other times it is bunch of errors saying something like: i/o error/end request/dev/sector ****, with all different sector numbers.. These happens even when I have not installed anything, not using any flash drives etc...
I have a flash drive that I regularly use on my laptop. If I unplug the flash drive without first unmounting it, I get a popup notification of a kernel failure (with diagnostics sent to kerneloops.org). Then, if I attempt to shut down the system via the console, it hangs on "The system is going down for halt/reboot NOW!" and doesn't actually shut down. Using Gnome's graphical System > Shut Down feature just logs me out and sends me to the login screen; the shutdown feature from there does nothing. I have to disconnect the power cord on the laptop in order to shut it down, and I don't like doing this.
System: 32-bit Debian Squeeze stable with kernel version 2.6.32-5-686, running Gnome 2.30.2, on an Acer Aspire 5570z.
I use Keepassx to store my passwords and keep the keyfile for my password database on the flash drive in question. I mention this just in case it helps determine what's causing the failure.
I recently switched from fedora 14 to 15. Today my computer suddenly shut down during an update, as I thought it overheated I decided to clean the cooling system and reapply thermal paste. However, now the system won't boot anymore ("kernel panic - not syncing : VFS: unable to mount root FS on unknown-block").
I would like to either solve this booting problem, or mount the fedora 15 filesystem and recover some files. Whichever is easier.
I have another drive with fedora 14 (antec below) which boots fine:
I don't know why "hibernate" disappear.It has swap on my fedora before.But I delete swap partition by accident.Does my problem has something related to this?
it's possible to compile the 2.6.37 kernel patched with the autogroup patch on a Slackware 13.1 system running 2.6.33.4-smp with 2.6.33.4 headers? I just compiled and installed the 2.6.37-autogroup kernel from AUR on my ARCH setup and I like it especially when using firefox with lots of tabs open and other background apps also running. I did notice a speed and smothness difference in my ARCH testing setup with this kernel patch and I can get same results in 13.1??
pls delete this post if I should not do this as it is included in [URL]..How do I recover from the 99 error when I start my system? I can only get to my Slackware by booting into it from the Slackware DVD.I have re-run lilo but I keep getting the 99 error on start up.
I am creating high CPU load on my system. Many large and huge files are copied between internal and external hard disks, and at the same time I am doing some office work and have a bunch of photos processed in a batch job.Looking at the system monitor, I can, however, see, that both CPU cores of my dual core processor are used heavily. But RAM beyond 2 GB is rarely used. Typically the maximum used RAM is 2 GB, no matter, how many files are copied and so on. Is this normal? I think, some of the tasks could be accomplished a lot faster, if the available RAM was used.
Where is the system locale set?When /etc/profile is run it sources /etc/profile.d/lang.sh which sets envar $LANG but /etc/profile is only used by login shells so -- AFAIK -- modifying $LANG in /etc/profile.d/lang.sh will not change the system locale for processes started by the boot scripts.There are no *locale* files under /etc./etc/inittab has nothing about locale.man init has nothing about locale.man 7 locale describes locale.h and its usage.man 5 locale describes the format of locale files./sbin/init (as investigated using the strings command) may call nl_langinfo but man nl_langinfo only describes how to query the locale, not where it is set.
I save my whole system to a .tar.gz file weekly except for the /proc content. I have used this backup a few times to restore my system without issue.
Last time I restored, I discovered the following 2 issues I home somebody can explain:
#1: while extracting the .tar.gz using tar xzvf filename.tar.gz, I get the following error near the end of the restore process "tar: Incorrect Length". This error only occurs when I boot the system with the slackware 12.1 disc 1 CD. It does not occur if I try to restore from my working system, same file. Other than this, everything seems to be restored properly and the system boots up properly. I am just concerned by the meaning of this error.
#2: After restore, I do lilo -C /mnt/etc/lilo.conf to make sure the systems boots up properly. This works... however, I have discovered that just this won't make module autoloading work after the restore. When booting the restored system, no module autoload !
I have correct this by just entering setup when booted up using the slackware 12.1 disk 1 CD and going thru addswap, set target without format and the going thru the configuration menu and cancelling all question.
I want to switch from my windows xp computer from Slackware Linux for my home pc.I use world and excel software and videos as well to watch movies how can I open my Ms office files in it? Does Slackware support yahoo messenger with voice ? What is the system requirement for slackware,the Ram,Processor and hard disk space for its latest version?
I'm trying to set up my system to act as a vnc so I can access it remotely via a vnc viewer on my android phone. I've never tried this before but from what I've found online, with KDE4 a lot of the usual vnc server programs won't work correctly. Anyone have any tips for getting it to work? It doesn't necessarily have to be vnc. If there's an alternative method to remote control of a computer, that will work too.
i am using Slackware 13.1 with my customize version of kernel:
# uname -a Linux dash-pc 2.6.33.4 #1 SMP Thu Dec 30 15:28:19 CET 2010 i686 Intel(R) Core(TM)2 Duo CPU T5670 @ 1.80GHz GenuineIntel GNU/Linux
I compiled into kernel CIFS module and now i am still not able to mount SAMBA directory.
# mount.cifs //192.168.0.101/music /home/dash/music Password: mount error: cifs filesystem not supported by the system mount error(19): No such device Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Is there an app that you can run before installing a new package etc and then after the install that will show you all the changes that occurred on your system as a result of installing the new package?
I am using slackware64-current and this morning I have updated my system with using slackpkg. (As you know, huge changes has been applied on the current branch. Kernel, glibc and etc..) Everything went flawness and seems OK. I did not see any error message or somethink like this. After the update, kde does not start. Problem is, after KDM login, nothing happens and turn back to KDM login screen.
To understand what is going on, I switched to init 3 and performed "startx" command. Result is same but I saw some dbus error.
Then I checked whether hald and dbus does run or not and I saw it is running without problem.
Lastly I have removed dbus and hald packages and reinstalled but problem is still running.
