Fedora 14 freezes

Frankster
Posts: 12
Joined: Fri Jul 22, 2011 10:48 am

Fedora 14 freezes

Postby Frankster » Fri Jul 22, 2011 10:56 am

Hi!

I´m a total newbie at Linux an so I hope you can help me :D

I installed Amahi last week and now I´m transfering my files to the shares.
That was now the second time that my system freezes.

I´m connected to the system via VNC (Windows --> Amahi).

I copied the data to Amahi and started greyhole -fsck
And then I lost my connection.
I´ve tried to go directly on the computer. But my monitor didn´t found a signal.

I searched in the Message file in the logs.
But there isn´t any entry with panic kernel ...

So how can I find the reason for the two freezes.

I´ve checked the RAM with memtest86+ --> OK
I´ve checked the drives --> OK
I´ve checked the CPU with mprime --> OK

This is my hardware
http://geizhals.at/eu/?cat=WL-151039

Many Thanks
Frankster

User avatar
radioz
Posts: 406
Joined: Tue Nov 24, 2009 1:07 pm

Re: Fedora 14 freezes

Postby radioz » Fri Jul 22, 2011 10:11 pm

So the hda video display was blank?

Did you have to boot up the hda again to get the display working?

This sounds like a hardware problem. Take a look at the log file in /var/log/messages.
Look for unusual error messages.

Let us know what you find.

Frankster
Posts: 12
Joined: Fri Jul 22, 2011 10:48 am

Re: Fedora 14 freezes

Postby Frankster » Sat Jul 23, 2011 3:35 am

Hi!

At the moment the Amahi server is standing next to me and is connected to my TFT with a second cable.
My working PC is also connected to the TFT, but I don´t want to switch every time, and so I configered VNC to get from my PC to the server.

Suddenly VNC lost the connection and so I switched my TFT from the PC to the server, but my TFT didnt found a signal.
I think the server was crashed/freezed at this moment.
http://hda also didnt worked.
And so I had to restart the server with the reset button.

To watch greyhole I used tail -f /var/log/greyhole.log
Mabey this was to much for the memory, because I transfered 360 gig to the server ?

WARNINGS:
Jul 17 09:09:10 amahi nmbd[2104]: Unable to find the Domain Master Browser name WORKGROUP<1b> for the workgroup WORKGROUP.
Jul 17 09:09:10 amahi nmbd[2104]: Unable to sync browse lists in this workgroup.
But I think this isnt a really problem
Jul 17 09:49:54 amahi kernel: [ 0.000000] ACPI Warning: Optional field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20100428/tbfadt-557)
ul 17 09:49:54 amahi kernel: [ 0.162277] ACPI Warning: Incorrect checksum in table [OEMB] - 0xF8, should be 0xF3 (20100428/tbutils-314)
Jul 17 09:49:56 amahi avahi-daemon[1570]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jul 17 09:49:56 amahi openvpn[1594]: WARNING: file '/etc/openvpn/amahi/server.key' is group or others accessible
Jul 17 09:50:02 amahi gnome-session[2249]: WARNING: AT-SPI: Accessibility bus not found - Using session bus.#012
Jul 17 09:50:02 amahi gdm-simple-greeter[2269]: WARNING: AT-SPI: Accessibility bus not found - Using session bus.#012
Jul 17 09:50:03 amahi gdm-simple-greeter[2269]: Gtk-WARNING: gtkwidget.c:5691: widget not within a GtkWindow
Jul 17 09:50:03 amahi gdm-simple-greeter[2269]: WARNING: Unable to load CK history: no seat-id found
Jul 17 13:04:42 amahi gdm-simple-greeter[2266]: WARNING: conversation gdm-fingerprint stopped when it shouldn't have been running (mode 2)
Jul 17 13:10:51 amahi gnome-session[2270]: WARNING: Client '/org/gnome/SessionManager/Client4' failed to reply before timeout
Jul 17 13:10:52 amahi gnome-session[2270]: WARNING: Unable to find desktop file 'gdm-simple-greeter.desktop': Es wurde keine gültige Schlüsselwertedatei in den Suchordnern gefunden
Jul 17 13:10:52 amahi gnome-session[2270]: WARNING: Unable to find desktop file 'gnome-gdm-simple-greeter.desktop.desktop': Es wurde keine gültige Schlüsselwertedatei in den Suchordnern gefunden
Jul 17 13:10:56 amahi gdm-simple-greeter[2290]: WARNING: Cancel org.freedesktop.DBus.Error.Disconnected raised: Connection was disconnected before a reply was received#012
Jul 17 13:10:56 amahi gdm-simple-greeter[2290]: WARNING: conversation gdm-fingerprint stopped when it shouldn't have been running (mode 2)
ERRORS:
Jul 17 09:49:07 amahi smbd[3390]: getpeername failed. Error was Der Socket ist nicht verbunden
Jul 17 09:49:07 amahi smbd[3390]: read_fd_with_timeout: client 0.0.0.0 read error = Die Verbindung wurde vom Kommunikationspartner zurückgesetzt.
Jul 17 09:49:54 amahi kernel: [ 6.266122] amd64_edac: probe of 0000:00:18.2 failed with error -22
Jul 17 09:50:23 amahi pulseaudio[2490]: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.DBus.Error.Spawn.ChildExited
interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply=0 destination=":1.9" (uid=0 pid=2232 comm="/usr/sbin/console-kit-daemon))
Jul 17 09:56:09 amahi pulseaudio[3264]: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.DBus.Error.Spawn.ChildExited
interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply=0 destination=":1.9" (uid=0 pid=2232 comm="/usr/sbin/console-kit-daemon))
Jul 17 10:14:01 amahi pulseaudio[3003]: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.DBus.Error.Spawn.ChildExited
Jul 17 10:14:01 amahi pulseaudio[3003]: main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-BdDMYxaCuF: Verbindungsaufbau abgelehnt
Jul 17 11:58:58 amahi smbd[3350]: [2011/07/17 11:58:58.782574, 0] lib/util_sock.c:1432(get_peer_addr_internal)
Jul 17 11:58:58 amahi smbd[3350]: getpeername failed. Error was Der Socket ist nicht verbunden
Jul 17 11:58:58 amahi smbd[3350]: getpeername failed. Error was Der Socket ist nicht verbunden
Jul 17 11:58:58 amahi smbd[3350]: write_data: write failure in writing to client 0.0.0.0. Error Die Verbindung wurde vom Kommunikationspartner zurückgesetzt
Jul 17 11:58:58 amahi smbd[3350]: Error writing 4 bytes to client. -1. (Der Socket ist nicht verbunden)
interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply=0 destination=":1.9" (uid=0 pid=2271 comm="/usr/sbin/console-kit-daemon))
Jul 18 19:31:42 amahi nmbd[2091]: [2011/07/18 19:31:42.746821, 0] nmbd/nmbd_browsesync.c:350(find_domain_master_name_query_fail)
PANIC
Jul 17 09:49:54 amahi kernel: [ 2.207020] drm: registered panic notifier
These are my Warning, error and panic meassages.
These messages are often to find

Many Thanks
Frankster

techlife
Posts: 63
Joined: Sat Dec 18, 2010 3:26 pm

Re: Fedora 14 freezes

Postby techlife » Tue Mar 20, 2012 6:36 pm

Was a solution ever found for this? I just upgraded to F14/A6 and am experiencing the same symptoms.

f1y
Posts: 1
Joined: Tue Mar 20, 2012 9:21 pm

Re: Fedora 14 freezes

Postby f1y » Tue Mar 20, 2012 9:30 pm

I'm having a similar prob, but I thgt it was because of old gear, i'm just about to try the express cd install, to see if that solves the prob.

My grafix are quite iffy in XP with this machinine as well.

I'm hoping to turn the old pc into an always on netwrok file server. Although i would love to be able to build an intranet site, that can seemlessy go onto the internet, with-out compromising secirity of the intranet.

Any suggestions on this would be welcome.

Bearing in mind I am a not fluent in geek.

so far have found it fairl y easy to get it working, bar the freezes from fedora.

Although I think I tweaked to many things last time as it caused problems with my internet access from my other PC.

fingers crossed and going headless will be the solution.

I'm ridiculously excited about getting this working.


oh, hi and cheers everyone.

User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: Fedora 14 freezes

Postby bigfoot65 » Wed Mar 21, 2012 4:42 am

The first key thing to check is if your system meets minimum requirements.

http://wiki.amahi.org/index.php/Requirements

If it does not, then your chance of success are slim.
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2

techlife
Posts: 63
Joined: Sat Dec 18, 2010 3:26 pm

Re: Fedora 14 freezes

Postby techlife » Wed Mar 21, 2012 7:06 am

I'll post my exact specs later when i get home, but I'm miles beyond the minimum requirements. I had no issues whatsoever until I upgraded to F14 this last week. Now, every time I try to copy media or do a backup, it freezes. Sometimes, it does all on its own. Very frustrating.

I've considered a fresh install but would like to avoid as it will take days to get everything configured back the way it is now with things like auto utorrent downloads, auto SQL backups, my xbmc SQL databases, etc. I'm going to have to if we can't find a solution by the weekend though as everything we watch lives on that server and the wife is about ready to make me sleep in e basement with the server.

[ Post made via iPad ] Image

User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: Fedora 14 freezes

Postby bigfoot65 » Wed Mar 21, 2012 7:13 am

Sorry to hear you might have to sleep in the basement LOL Upgrading is not always the ideal path. It might be beneficial to do a fresh install. Although it's a lot of work to get it back where you want it, might prevent future issues.

Maybe once you can find what it causing the freeze, it will be a simple fix. Might be some sort of hardware driver that is different in Fedora 14.

Now with that said, when Amahi for Fedora 16 is ready it might not have an upgrade path. Given that situation, it might be best to hold out as long as you can.

Unfortunately I cannot give you a good estimate as to when it will be ready for prime time. There is still some work being done and it is likely the release will be slipped into April.
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2

techlife
Posts: 63
Joined: Sat Dec 18, 2010 3:26 pm

Re: Fedora 14 freezes

Postby techlife » Thu Mar 22, 2012 6:06 am

Is this of interest to you? (I think) It's the only thing I haven't been able to fix so far in messages:

Code: Select all

Mar 21 22:58:16 Xavier kernel: [97970.988599] possible SYN flooding on port 59670. Sending cookies. Mar 21 23:01:35 Xavier kernel: [98169.325849] possible SYN flooding on port 59670. Sending cookies. Mar 21 23:11:29 Xavier kernel: [98763.306857] possible SYN flooding on port 59670. Sending cookies. Mar 21 23:12:31 Xavier kernel: [98826.220704] possible SYN flooding on port 59670. Sending cookies. Mar 21 23:13:37 Xavier kernel: [98891.675905] possible SYN flooding on port 59670. Sending cookies. Mar 22 03:37:39 Xavier smbd_greyhole: [2012/03/22 03:37:39.775521, 0] lib/util_sock.c:474(read_fd_with_timeout) Mar 22 03:37:39 Xavier smbd_greyhole: [2012/03/22 03:37:39.793917, 0] lib/util_sock.c:1441(get_peer_addr_internal) Mar 22 03:37:39 Xavier smbd_greyhole: getpeername failed. Error was Transport endpoint is not connected Mar 22 03:37:39 Xavier smbd_greyhole: read_fd_with_timeout: client 0.0.0.0 read error = No route to host. Mar 22 03:42:13 Xavier smbd_greyhole: [2012/03/22 03:42:13.877472, 0] lib/util_sock.c:474(read_fd_with_timeout) Mar 22 03:42:13 Xavier smbd_greyhole: [2012/03/22 03:42:13.877691, 0] lib/util_sock.c:1441(get_peer_addr_internal) Mar 22 03:42:13 Xavier smbd_greyhole: getpeername failed. Error was Transport endpoint is not connected Mar 22 03:42:13 Xavier smbd_greyhole: read_fd_with_timeout: client 0.0.0.0 read error = No route to host. Mar 22 03:59:57 Xavier smbd_greyhole: [2012/03/22 03:59:57.350561, 0] lib/util_sock.c:474(read_fd_with_timeout) Mar 22 03:59:57 Xavier smbd_greyhole: [2012/03/22 03:59:57.350784, 0] lib/util_sock.c:1441(get_peer_addr_internal) Mar 22 03:59:57 Xavier smbd_greyhole: getpeername failed. Error was Transport endpoint is not connected Mar 22 03:59:57 Xavier smbd_greyhole: read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. Mar 22 04:02:32 Xavier smbd_greyhole: [2012/03/22 04:02:32.983175, 0] lib/util_sock.c:474(read_fd_with_timeout) Mar 22 04:02:33 Xavier smbd_greyhole: [2012/03/22 04:02:32.997923, 0] lib/util_sock.c:1441(get_peer_addr_internal) Mar 22 04:02:33 Xavier smbd_greyhole: getpeername failed. Error was Transport endpoint is not connected Mar 22 04:02:33 Xavier smbd_greyhole: read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. Mar 22 04:14:41 Xavier kernel: [116956.070165] r8169 0000:02:00.0: eth0: link up
I didn't think this was a greyhole problem at first, but now I'm starting to wonder...This event is when one of the ATVs in the house rebooted. I will try copying a file over tonight when I get home and see if I can find anything else of interest in the log.

techlife
Posts: 63
Joined: Sat Dec 18, 2010 3:26 pm

Re: Fedora 14 freezes

Postby techlife » Sun Mar 25, 2012 7:55 am

OK, squeaky clean install of F14/Amahi 6. Same issue. Try to copy a large file, server freezes solid.

What can I do to get this straight? Very, very frustrated.

FWIW, here's what I'm seeing in messages. Don't know if it's related or not.

Code: Select all

Mar 25 08:34:23 hda smbd_greyhole: [2012/03/25 08:34:23.937176, 0] lib/util_sock.c:474(read_fd_with_timeout) Mar 25 08:34:23 hda smbd_greyhole: [2012/03/25 08:34:23.942915, 0] lib/util_sock.c:1441(get_peer_addr_internal) Mar 25 08:34:23 hda smbd_greyhole: getpeername failed. Error was Transport endpoint is not connected Mar 25 08:34:23 hda smbd_greyhole: read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. Mar 25 08:36:47 hda smbd_greyhole: [2012/03/25 08:36:47.950295, 0] lib/util_sock.c:474(read_fd_with_timeout) Mar 25 08:36:47 hda smbd_greyhole: [2012/03/25 08:36:47.950503, 0] lib/util_sock.c:1441(get_peer_addr_internal) Mar 25 08:36:47 hda smbd_greyhole: getpeername failed. Error was Transport endpoint is not connected Mar 25 08:36:47 hda smbd_greyhole: read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. Mar 25 08:42:32 hda ntpd[2253]: 0.0.0.0 c612 02 freq_set kernel -247.673 PPM Mar 25 08:42:32 hda ntpd[2253]: 0.0.0.0 c615 05 clock_sync Mar 25 08:42:48 hda nmbd[2574]: [2012/03/25 08:42:48.661805, 0] nmbd/nmbd_browsesync.c:350(find_domain_master_name_query_fail) Mar 25 08:42:48 hda nmbd[2574]: find_domain_master_name_query_fail: Mar 25 08:42:48 hda nmbd[2574]: Unable to find the Domain Master Browser name TECHLIFE<1b> for the workgroup TECHLIFE. Mar 25 08:42:48 hda nmbd[2574]: Unable to sync browse lists in this workgroup.
And the samba log for the client trying to copy to the server:

Code: Select all

read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. [2012/03/25 07:19:00.292680, 0] lib/util_sock.c:474(read_fd_with_timeout) [2012/03/25 07:19:00.292936, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. [2012/03/25 08:32:56.151503, 0] smbd/nttrans.c:2271(call_nt_transact_ioctl) call_nt_transact_ioctl(0x90248): Currently not implemented.
What else do I need to provide? I really need to get this fixed. Please.

Who is online

Users browsing this forum: No registered users and 51 guests