View Single Post
  #20  
Old 16th August 2006, 21:26
jonathankinney jonathankinney is offline
Junior Member
 
Join Date: Aug 2006
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default The reason the service control hung

I can tell you that this problem where switching a service off/on does not work any more due to the "/root/ispconfig/scripts/writeconf.php" process dieing on a SIGSEGV (Segmentation fault) is not in fact bad ram or hard drive. This problem is one that can be reproduced on different systems and different installations, but I can only speak for the installations based on Fedora Core 4.
On closer inspection (after removing the /root/ispconfig/.ispconfig_lock) when running the process through strace:

strace -f /root/ispconfig/php/php /root/ispconfig/scripts/writeconf.php

The segmentation fault happens when it is reading data from the dns_isp_dns table. It is the data in that table that some how causes /root/ispconfig/scripts/writeconf.php to die with a segmentation fault. You have to keep in mind that when you are dealing with PHP, there are software causes for segmentation faults, as in errors or situations in the code that cause unhandled problems with that PHP interpreter process. This is one of those cases. I just removed the single DNS entry from the table, and ran through the process again, no problems at all. The contents of the dns_isp_dns table was as follows:

Code:
+--------+------------+-----------------+-------------+-----------+------------+---------+-------------------------------+-------------------------------+-----------------------+-----------+--------+--------------+
| doc_id | doctype_id | dns_soa         | dns_refresh | dns_retry | dns_expire | dns_ttl | dns_ns1                       | dns_ns2                       | dns_adminmail         | server_id | status | dns_soa_ip   |
+--------+------------+-----------------+-------------+-----------+------------+---------+-------------------------------+-------------------------------+-----------------------+-----------+--------+--------------+
|      1 |       1016 | norealdomai.net | 28800       | 7200      | 604800     | 86400   | virtuozzo-fc4.norealdomai.net | virtuozzo-fc4.norealdomai.net | admin@norealdomai.net | 1         | d      | 10.254.138.14 |
+--------+------------+-----------------+-------------+-----------+------------+---------+-------------------------------+-------------------------------+-----------------------+-----------+--------+--------------+
The domain and IP address were the only things that were modified for privacy sake. If anyone has any questions, or would like more information, I do have the full strace on file. I discovered this by finding why one of my installations was having this problem, when the other was not. Well it turns out, my other installation had no DNS entries set up.
__________________
Jonathan Kinney
Data Systems Specialist
Advantagecom Networks, Inc.
http://www.simplywebhosting.com
Reply With Quote