drkwtsn Posted April 19, 2006 Share Posted April 19, 2006 while letting my parity disk build overnight, my machine seem to of frozen so I rebooted the machine this morning and started building the disk again. The build got all the way to around 47% and then when i went to check it again, the webpage is unaccesable... (tries to get to it, but just sits there loading and loading, never comes up, then page cannot be displayed.... same thing that happened last night....).. shortly before this happened though the time went from 230 mins or so to 1900 mins remaining (no data was being copied)... Anyone have any idea whats going on? Link to comment
lovingHDTV Posted April 19, 2006 Share Posted April 19, 2006 Try this: After rebooting and seeing the parity build start. open a command window in XP and telnet to tower then type: tail -f /var/log/syslog This should print out to the command window what is happening. Then when it hangs you may be able to see an error message or something similar. Link to comment
drkwtsn Posted April 19, 2006 Author Share Posted April 19, 2006 its still building, but here are the messages i am getting so far FileServer login: root Linux 2.4.29. root@FileServer:~# tail -f /var/log/syslog Apr 20 01:46:02 FileServer kernel: get_token: check Apr 20 01:46:02 FileServer kernel: md: recovery thread syncing parity disk... Apr 20 01:46:02 FileServer kernel: md: writing superblock to device sda2 Apr 20 01:46:04 FileServer kernel: get_token: status Apr 20 01:47:09 FileServer kernel: get_token: status Apr 20 01:48:31 FileServer kernel: get_token: status Apr 20 01:48:43 FileServer last message repeated 2 times Apr 20 02:00:40 FileServer smbd[837]: [2006/04/20 02:00:40, 0] lib/util_sock.c:r ead_socket_data(384) Apr 20 02:00:40 FileServer smbd[837]: read_socket_data: recv failure for 4. Er ror = Connection reset by peer Apr 20 02:13:36 FileServer kernel: get_token: status Apr 20 02:20:14 FileServer kernel: get_token: status Apr 20 02:26:52 FileServer kernel: get_token: status Apr 20 02:29:15 FileServer kernel: get_token: status Apr 20 02:32:41 FileServer smbd[852]: [2006/04/20 02:32:41, 0] lib/util_sock.c:r ead_socket_data(384) Apr 20 02:32:41 FileServer smbd[852]: read_socket_data: recv failure for 4. Er ror = Connection reset by peer Apr 20 02:41:54 FileServer kernel: get_token: status Apr 20 02:43:34 FileServer kernel: get_token: status Apr 20 02:47:42 FileServer kernel: get_token: status Apr 20 02:52:00 FileServer kernel: get_token: status Apr 20 03:01:15 FileServer kernel: get_token: status Apr 20 03:02:30 FileServer kernel: get_token: status Apr 20 03:03:21 FileServer kernel: get_token: status Apr 20 03:04:41 FileServer smbd[877]: [2006/04/20 03:04:41, 0] lib/util_sock.c:g et_peer_addr(1000) Apr 20 03:04:41 FileServer smbd[877]: getpeername failed. Error was Transport endpoint is not connected Apr 20 03:04:41 FileServer smbd[877]: [2006/04/20 03:04:41, 0] lib/util_sock.c:w rite_socket_data(430) Apr 20 03:04:41 FileServer smbd[877]: write_socket_data: write failure. Error = Connection reset by peer Apr 20 03:04:41 FileServer smbd[877]: [2006/04/20 03:04:41, 0] lib/util_sock.c:w rite_socket(455) Apr 20 03:04:41 FileServer smbd[877]: write_socket: Error writing 4 bytes to s ocket 6: ERRNO = Connection reset by peer Apr 20 03:04:41 FileServer smbd[877]: [2006/04/20 03:04:41, 0] lib/util_sock.c:s end_smb(647) Apr 20 03:04:41 FileServer smbd[877]: Error writing 4 bytes to client. -1. (Co nnection reset by peer) Link to comment
drkwtsn Posted April 19, 2006 Author Share Posted April 19, 2006 the website seems to be down now to access the box this is the last of the logs Apr 20 03:10:03 FileServer kernel: get_token: status Apr 20 03:14:47 FileServer kernel: get_token: status Apr 20 03:26:13 FileServer kernel: get_token: status Apr 20 03:36:41 FileServer smbd[881]: [2006/04/20 03:36:41, 0] lib/util_sock.c:r ead_socket_data(384) Apr 20 03:36:41 FileServer smbd[881]: read_socket_data: recv failure for 4. Er ror = Connection reset by peer I am still able to do things in telnet though, any ideas? edit::: connection was lost via telnet, went back in and saw these messages Apr 20 04:08:43 FileServer smbd[919]: [2006/04/20 04:08:43, 0] lib/util_sock.c:r ead_socket_data(384) Apr 20 04:08:43 FileServer smbd[919]: read_socket_data: recv failure for 4. Er ror = Connection reset by peer Link to comment
drkwtsn Posted April 21, 2006 Author Share Posted April 21, 2006 Apparently everything is ok now... The problem seemed to be with the router, not the server freezing up at all. I installed a new router and everything is working fine... parity drive is built and ready to go Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.