In addition to a possibility of the config files being stored in a temporary directory (unable to substantiate it without code), there is also the possibility that some code path in your code allows the configuration files to be removed by some invocation of your code.
I would do the following things (for starters):
- Check for any security advisories on your software, and apply fixes for those issues. This is extremely important for any public-facing server, not just web servers.
- check your configuration files and settings to ensure that you are not storing them in an area that gets periodically cleaned.
- Check to see that there are no external cleanup (or other) processes that can delete these files (see at, cron, windows scheduled tasks, and so on). I once saw a situation where important files on a shared filesystem were removed by a find process on another machine, because of a '-follow' flag and a symlink in a /tmp directory.
Additionally, you may want to get familiar with your code and learn how to (or contract with someone to) do a code audit on your system. There are monks around who make themselves available for consulting of this type.
| [reply] |
Am I barking up the wrong tree or could it be that there are two different clocks (so to speak) at the server end? Very unlikely, but not inconceivable ( virtual machines , rogue time server, broken time daemons ... )
and if there were and they were out of sync would this explain why, at my end, it randomly stops being able to find the files? No. If it is too old, it will still be there. Chances are you have a coding error -- or doing something bizzare like keeping the config file in a temp directory which gets emptied every 2-3 days.
| [reply] |
Thank you both.
I should have mentioned that it's a pretty old site and has been working for nearly 10 years.
Config not in a temp directory.
Possibility of a new vulnerability? I guess but it's no longer supported.
No files get deleted. They are where they always have been.
It has a setup interface accessed by deleting the location.pl file.
To restart I merely delete the timestamps and recreate the location.pl.
It's not the location file that's the problem as it times out while looking in the correct folder for a file that is there and does have the correct permissions.
Timestamps are the only files that get renewed.
To be honest, the entire site is being retired in a couple of weeks but it bugs me if I don't have logical explanations for things.
I was sure it was at the server end (ref two different sites having the same problem) but a new vulnerability is a real possibility. Thank You Both!!!
| [reply] |