Had a problem last week on a Links SQL v2 site, where the system became inaccessible and I kept getting error messages along the lines of "configdata.pm did not return a hash value".
On closer investigation, configdata.pm was 0 bytes long. Restoring a backup copy of the file fixed the problem.
The situation was caused because the server ran out of disk space. Consequently, Links SQL was unable to update its config file and this had resulted in the file being wiped.
I'm not sure whether Gossamer Links v3 handles the full-drive situation better than version 2 does, but I guess I will find out next week when I attempt to upgrade.
Just thought this might be of interest to some people.
On closer investigation, configdata.pm was 0 bytes long. Restoring a backup copy of the file fixed the problem.
The situation was caused because the server ran out of disk space. Consequently, Links SQL was unable to update its config file and this had resulted in the file being wiped.
I'm not sure whether Gossamer Links v3 handles the full-drive situation better than version 2 does, but I guess I will find out next week when I attempt to upgrade.
Just thought this might be of interest to some people.
