I've been using DBMan since it first came out. This problem has me stumped. I'll enter some records (benign ASCII text w/some HTML list tags for a job database) and it will run just fine -- save/modify/delete, etc.
Moments later I will try to add or modify a record, and it just sits there, working, but nothing's happening.
A quick check of the processes on the box (Apache on BSD) shows no runaway Perl activity. Nothing is set wrong; all permissions are OK. Like I said, this was running fine when a customer brought to my attention she all of a sudden could not add new records, it just hung.
There are no error messages; the Web browser process bar just runs, and runs, then the page times out.
My guess at first was that there was something wrong with the server, although nothing has been done it recently. I have a duplicate test server which ran the program just fine, however, after a while of testing it thouroughly, it too demonstrated this behavior.
My question, has anyone seen this "timed-out" behavior? If so, what was the problem?
Thanks,
Shawn
Seattle, WA
Moments later I will try to add or modify a record, and it just sits there, working, but nothing's happening.
A quick check of the processes on the box (Apache on BSD) shows no runaway Perl activity. Nothing is set wrong; all permissions are OK. Like I said, this was running fine when a customer brought to my attention she all of a sudden could not add new records, it just hung.
There are no error messages; the Web browser process bar just runs, and runs, then the page times out.
My guess at first was that there was something wrong with the server, although nothing has been done it recently. I have a duplicate test server which ran the program just fine, however, after a while of testing it thouroughly, it too demonstrated this behavior.
My question, has anyone seen this "timed-out" behavior? If so, what was the problem?
Thanks,
Shawn
Seattle, WA