Workstations shutting down for no apparent reason (F8)
by Alain Cochard
Hello. I am running 40 workstations with 3 kinds of hardware, all
under fedora 8. From time to time -- about once every 3 days -- one
of the machine (not always the same) shuts itself down. Otherwise
they are running 24 hours a day every day.
The excerpt of the /var/log/messages that seems relevant to me is
always similar to the following:
Nov 18 15:12:26 epgs16 acpid: received event "button/power PWRF 00000080 00000001"
Nov 18 15:12:26 epgs16 acpid: notifying client 2271[68:68]
Nov 18 15:12:26 epgs16 acpid: notifying client 2467[0:0]
Nov 18 15:12:26 epgs16 acpid: client has disconnected
Nov 18 15:12:26 epgs16 acpid: notifying client 2467[0:0]
Nov 18 15:12:26 epgs16 acpid: client has disconnected
Nov 18 15:12:26 epgs16 acpid: notifying client 2467[0:0]
Nov 18 15:12:26 epgs16 acpid: executing action "/bin/ps awwux | /bin/grep gnome-power-manager | /bin/grep -qv grep || /sbin/shutdown -h now"
Nov 18 15:12:26 epgs16 shutdown[19479]: shutting down for system halt
Nov 18 15:12:26 epgs16 acpid: action exited with status 0
Nov 18 15:12:26 epgs16 acpid: completed event "button/power PWRF 00000080 00000001"
Nov 18 15:12:27 epgs16 avahi-daemon[2211]: Got SIGTERM, quitting.
Nov 18 15:12:27 epgs16 avahi-daemon[2211]: Leaving mDNS multicast group on interface eth0.IPv4 with address 130.79.9.36.
Nov 18 15:12:28 epgs16 hcid[2040]: Stopping SDP server
Nov 18 15:12:28 epgs16 hcid[2040]: Unregister path: /org/bluez
Nov 18 15:12:28 epgs16 input[2065]: Unregistered manager path
Nov 18 15:12:28 epgs16 input[2065]: Exit
Nov 18 15:12:28 epgs16 hcid[2040]: Shutting down local server
Nov 18 15:12:28 epgs16 hcid[2040]: Exit
Nov 18 15:12:28 epgs16 acpid: exiting
Nov 18 15:12:28 epgs16 kernel: Kernel logging (proc) stopped.
Nov 18 15:12:28 epgs16 kernel: Kernel log daemon terminating.
Nov 18 15:12:29 epgs16 rsyslogd: [origin software="rsyslogd" swVersion="1.19.6" x-pid="1974"] exiting on signal 15.
Thanks in advance for any tip on how to solve this problem.
Alain
15 years, 6 months
Fedora 10 Boot hang
by Duane Morris
Just tried the new Fedore 10 DVD iso, installes fine, then I reboot and it hangs.
sdb: sdb1 sdb2
sd 0:0:8:0: [sdb] attached SCSI Disk
sd 0:0:8:0: [sdb] attached SCSI generic sq1 type 0
And then I'm toast. Any Ideas
Thanks
Duane
15 years, 6 months
SANE can't find device if used through VNC - F9
by redhatdude＠bellsouth.net
Hello,
I got a F9 machine that I access through VNC. If I'm at the machine, I can open SANE and scan without any problems. If I, however, do this remotely through VNC, SANE cannot find my HP scanner.
I tried the same using X11 from a Mac and it didn't work either. However, if I login as root and launch SANE, it works, if finds the scanner and scans.
Any idea how to solve this issue?
Thanks,
EJ
15 years, 6 months
F10: devicemapper raid not seen in installer
by David Jansen
After a few succesful Fedora 10 installs, I tried to install my main
machine which has 3 harddisks, 1 SATA disk (sda) for the system and a
data partition, and 2 sata disks in RAID1, set through the bios (Intel
chipset, raid bios reports as Intel Matrix Storage Manager option ROM
v7.6.0.1011 ICH9R wRAID5) which in Fedora 8 was handled by device mapper:
$ df /home
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/isw_edcfaihjg_Volume0p1
473078128 106809904 341849428 24% /home
However, when starting a fresh install of Fedora 10 (I wanted to keep
/home and /data, but reformat the other partitions), no RAID was seen;
anaconda just reports 3 SATA disks, sa, sdb and sdc, and sdb and sdc
both contain 1 ext3 partion, both labeled /home , according to anaconda.
Is there some additional magic or boot option needed to enable
devicemapper during a reinstall? I couldn't find anything in the release
notes that could indicate that this behaviour has changed.
David Jansen
PS: in case it helps, architecture is x86_64; system is a HP xw4600, cpu
reports as Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
15 years, 6 months
decrypting iptables?
by Tom Horsley
Being bored at the end of the holidays I am foolishly
attempting to understand how to setup iptables. I
did a "yum install firestarter" and tried it. The GUI
it has may be slightly less cryptic that the low
level iptables config files, but not much, and just
about the time I'm able to think I may have it
figured out, it aborts on me :-). Any other less
cryptic GUI options (I know about system-config-firewall,
but it is way too simplistic to let me setup the rules
I want).
15 years, 6 months
F10 NFS Install Query
by Dr J Austin
Hi
Previous versions of Fedora just needed the .iso file
on the server for an NFS install
For F10 I needed to mount the file in loopback and copy the contents of
the DVD to a separate directory before
anaconda could find it - is this a bug or a feature?
Does anyone know if NFS exporting a loop mounted file
is possible. I could not see it when I tried this.
I did not want to fiddle with my main server too much
Would the nohide option in /etc/exports do the trick ?
John
15 years, 6 months
Borked MD RAID...
by Eitan Tsur
I just recently installed a 3-disk RAID5 array in a server of mine, running
FC9. Upon reboot, one of the drives drops out, and is allocated as a spare.
I suspect there is some sort of issue where DBUS re-arranges the
drive-to-device maps between boots, but I am not sure... Just kind of
annoying to have to stop and re-add a drive every boot, and wait the couple
hours for the array to rebuild the 3rd disk. Any thoughts? Anyone else
encountered such an issue before? What should I be looking for? I'm new to
the world of RAID, so any information you can give may be helpful.
Regards,
-Eitan-
15 years, 6 months
Trying to install NX
by Jim
Fedora 8 x86_64
Trying to install NX.
I have no problem connecting other i386 boxes.
Error messages below;
This is the output of NXClient on Laptop
NXPROXY - Version 3.1.0
Copyright (C) 2001, 2007 NoMachine.
See http://www.nomachine.com/ for more information.
Info: Proxy running in client mode with pid '17226'.
Session: Starting session at 'Sat Feb 9 15:43:20 2008'.
Info: Connection with remote proxy completed.
Info: Using ADSL link parameters 512/24/1/0.
Info: Using cache parameters 4/4096KB/16384KB/16384KB.
Info: Using pack method 'adaptive-7' with session 'kde'.
Info: Using product 'LFE/None/LFEN/None'.
Info: Using ZLIB data compression 1/1/32.
Info: Using ZLIB stream compression 4/4.
Info: No suitable cache file found.
Info: Forwarding X11 connections to display ':0.0'.
Info: Listening to font server connections on port '11004'.
Session: Session started at 'Sat Feb 9 15:43:20 2008'.
Info: Established X server connection.
Info: Using shared memory parameters 1/4096K.
Error: Connection with remote peer broken.
Error: Please check the state of your network and retry.
Session: Terminating session at 'Sat Feb 9 15:43:24 2008'.
Session: Session terminated at 'Sat Feb 9 15:43:24 2008'.
This is the server box x86_64 /messages file
Feb 9 15:43:10 x86_64 NXSERVER-3.1.0-4[6223]: User 'mickey' logged in from '76.251.280.83'. 'NXLogin::set'
Feb 9 15:43:13 x86_64 NXSERVER-3.1.0-4[6223]: Selected node host:localhost with port:22 'main::selectNode'
Feb 9 15:43:13 x86_64 NXSERVER-3.1.0-4[6223]: Current selected node: localhost is in status: running 'main::selectNode'
Feb 9 15:43:13 x86_64 NXSERVER-3.1.0-4[6223]: Selected session type: unix-kde allowed in the profile of user: mickey 'NXShell::Static'
Feb 9 15:43:15 x86_64 NXSERVER-3.1.0-4[6223]: ERROR: nxssh process exited with '255' 'NXNodeExec::exec'
Feb 9 15:43:19 x86_64 NXSERVER-3.1.0-4[6223]: Session '7F7FA6AC9A8C13F31E8F8EC3BAA37650' started by user 'mickey'. 'NXShell::handler_session_start'
Feb 9 15:43:19 x86_64 NXSERVER-3.1.0-4[6223]: ERROR: run command: no child process with pid 6330 Logger::log nxserver 3069
Feb 9 15:43:19 x86_64 NXSERVER-3.1.0-4[6223]: User 'mickey' from '76.251.280.83' logged out. 'NXLogin::reset'
Feb 9 15:43:19 x86_64 NXNODE-3.1.0-5[6371]: Using port '1004' on node 'x86_64' for session 'unix-kde'. Logger::log nxnode 5975
Feb 9 15:43:19 x86_64 NXNODE-3.1.0-5[6371]: Using host from available host list: '172.16.1.36'. Logger::log nxnode 5976
Feb 9 15:43:20 x86_64 NXNODE-3.1.0-5[6735]: ERROR: Error when monitoring session: Could not open default font 'fixed' 'NXSessionMonitor::__setSessionStatus'
Feb 9 15:43:20 x86_64 NXNODE-3.1.0-5[6735]: NXSessionMonitor: killing unexpected agent running with pid '6653' with signal '15' 'NXSessionMonitor::monitorStatus'
Feb 9 15:43:23 x86_64 NXNODE-3.1.0-5[6735]: NXSessionMonitor: killing unexpected agent running with pid '6653' with signal '15' 'NXSessionMonitor::monitorStatus'
Feb 9 15:43:24 x86_64 NXNODE-3.1.0-5[6735]: NXSessionMonitor: killing unexpected agent running with pid '6653' with signal '9' 'NXSessionMonitor::monitorStatus'
Feb 9 15:43:24 x86_64 NXNODE-3.1.0-5[6371]: ERROR: Unexpected termination of nxagent because of signal: 9 Logger::log nxnode 3777
Feb 9 15:43:24 x86_64 NXNODE-3.1.0-5[6371]: ERROR: run command: process: 6653 died because of signal: 9 Logger::log nxnode 3784
Feb 9 15:43:25 x86_64 NXNODE-3.1.0-5[6735]: Directory '/home/mickey/.nx/C-x86_64-1004-7F7FA6AC9A8C13F31E8F8EC3BAA37650' renamed into '/home/mickey/.nx/F-C-x86_64-1004-7F7FA6AC9A8C13F31E8F8EC3BAA37650' for further investigation Logger::log nxnode 6155
Feb 9 15:43:26 x86_64 NXNODE-3.1.0-5[6371]: Session 'unix-kde' on port '1004' failed. Logger::log nxnode 6234
Feb 9 15:43:32 x86_64 NXSERVER-3.1.0-4[6656]: ERROR: NXNodeExec: Cannot kill nxssh process: No such process 'NXNodeExec::exec'
Feb 9 15:43:32 x86_64 NXSERVER-3.1.0-4[6656]: User 'mickey' from '76.251.280.83' logged out. 'NXLogin::reset'
15 years, 6 months
Problems with kdm in F10
by Marcelo Magno T. Sales
People,
I've just installed F10 and have fully updated the system.
When I replace gdm with kdm, I can only log in to KDE using the root
account. When I try to log in using a regular user account, I get the
following error message:
"Cannot enter home directory. Using /."
When I click ok, I get this other one:
"Could not start kstartupconfig4. Check your installation."
If I revert to gdm, everything is fine again. What may be causing this
problem?
Also, user photos are not shown in kdm. The default image is displayed
for every user, despite they all have their photos configured since
before F10 was installed. I did a fresh install of F10 (didn't upgrade
from F9), but the /home file system was not modified. The user photos
still appear in Kickoff. KDM was configured with System Configuration to
show preferentially the user photos and use the default image only if
users have not provided their own photos. Why aren't the user photos
displayed in kdm?
Thanks,
Marcelo
15 years, 6 months
