Segmentation fault

E

elbarto

Verified User
Joined
Oct 8, 2008
Messages
134
I'm getting a segmentation fault when I try to run directadmin. It was working fine until a couple of hours ago. It stopped working. I logged in to my server and saw it throws a segfault.

Code: 
$ /usr/local/directadmin/directadmin d
Segmentation fault

I tryied to run gdb but got this error:

Code: 
[root@myserver directadmin]# gdb directadmin 
GNU gdb Red Hat Linux (6.5-37.el5rh)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"..."/usr/local/directadmin/directadmin": not in executable format: File format not recognized

Can you help me to fix it? I need to fix it ASAP, because I have lots of clients complaining.

Thanks in advance
 
What did you do between the time it was working and the time it stopped working?
 
I personally did nothing, but I think there was some update during the night.
I have some errors on directadmin's error.log.
I changed sensible information for security reasons:

Code: 
2010:01:05-14:02:55: Socket write error: fd is connected to a pipe or socket whose reading end is closed.  When this  happens the writing process will also receive a SIG_PIPE signal.  (Thus, the write return value is seen only if  the program catches, blocks or ignores this signal.)
2010:01:05-14:02:55: Error reading from 2.2.2.2: 
2010:01:05-14:02:55: Socket write error: fd is connected to a pipe or socket whose reading end is closed.  When this  happens the writing process will also receive a SIG_PIPE signal.  (Thus, the write return value is seen only if  the program catches, blocks or ignores this signal.)
2010:01:05-14:02:55: Error reading from 2.2.2.2: 
2010:01:05-14:02:58: Socket write error: fd is connected to a pipe or socket whose reading end is closed.  When this  happens the writing process will also receive a SIG_PIPE signal.  (Thus, the write return value is seen only if  the program catches, blocks or ignores this signal.)
2010:01:05-14:02:58: Error reading from 2.2.2.2: 
2010:01:05-15:05:00: Socket write error: fd is connected to a pipe or socket whose reading end is closed.  When this  happens the writing process will also receive a SIG_PIPE signal.  (Thus, the write return value is seen only if  the program catches, blocks or ignores this signal.)
2010:01:05-15:05:00: Error reading from 3.3.3.3: 
2010:01:05-15:05:29: Socket write error: fd is connected to a pipe or socket whose reading end is closed.  When this  happens the writing process will also receive a SIG_PIPE signal.  (Thus, the write return value is seen only if  the program catches, blocks or ignores this signal.)
2010:01:05-15:05:29: Error reading from 3.3.3.3: 
2010:01:05-15:21:47: User::removeUserFromCreator(fperez, verianet) verianet doesn't exists or usertype is messed up
2010:01:05-22:17:11: Error reading from 1.1.1.1: 
2010:01:05-22:22:31: Error reading from 1.1.1.1: 
2010:01:05-22:23:00: Error reading from 1.1.1.1: 
2010:01:05-22:23:04: Error reading from 1.1.1.1: 
2010:01:05-22:23:11: Error reading from 1.1.1.1: 
2010:01:05-22:23:51: Error reading from 1.1.1.1: 
2010:01:05-22:24:05: Error reading from 1.1.1.1: 
2010:01:05-22:24:12: Error reading from 1.1.1.1: 
2010:01:05-22:24:23: Error reading from 1.1.1.1: 
2010:01:05-23:17:18: Socket write error: Unknown error
2010:01:05-23:17:18: Error while sending ./data/skins/Marina/images/user.gif

The IPs which I replaced by "1.1.1.1" and "2.2.2.2", I don't know them. The IP "3.3.3.3" is my server's IP address. Before these lines, I see similar errors with "Error reading from", but the IP change. I have some with other IPs of the same network as 1.1.1.1, i.e: 1.1.1.2 and 1.1.1.3. I tried to ping all those IPs but they do not respond. I'm not sure if this is an important error or if I should look somewhere else.
 
I just found this on the errortaskq.log

Code: 
2010:01:06-04:04:25: Unable to Update the software!: Error restoring file /usr/local/directadmin/update.tar.gz : 
gzip: stdin: unexpected end of file
/bin/tar: Unexpected EOF in archive
/bin/tar: Unexpected EOF in archive
/bin/tar: Error is not recoverable: exiting now
 : tar returned error code 512<br>
<br>
<br>
Try updating manually: http://help.directadmin.com/item.php?id=29<br>


I'll try to update manually and let you know.
 
Search on google:

Code: 
"Socket write error: fd is connected to a pipe or socket whose reading end is closed" site:directadmin.com

Variety of answers.
 
You must log in or register to reply here.
Back
Top