| Steve Jones wrote: |
| Steve Jones wrote: |
| Stefan Ritt wrote: |
No, the above link just works fine, just click it. |
| Quote: | I was afraid to try  . Ok, then the issue *might* be rev 1660. On my production version running 2.5.3 I get the expected "Invalid URL: <name>" box. Any suggestions on how to find out? |
|
| Steve Jones wrote: | Ok, here is what I found:
- Now running rev 1671
- Specifying a non-existent logbook with plain URL of elog server: OK, error is caught and reported
- Specifying a non-existent logbook *under* a logbook name: Ok, error is caught.
- Specifying a non-existent logbook under a "Top Group" of the form "This+Is+Top+Group+One" results in no error, elogd crash. Example URLs:
- Results in a program crash under Solaris. Top Groups were not defined under elog 2.5.3.
|
|
| Steve Jones wrote: | Well, more data. When I have Top Groups defined and I go to create a new logbook via the eLog interface, the interface creates a URL of the form:http://elog-test.company.com/EngineeringComputeChangeLogs/Test2/?cmd=Config
This causes eLog to crash -- so I am at a complete loss. I tried shortening the length of the top group name. It all seems to come back to the inclusion of the name of a logbook that doesn't exist yet?) although I confirmed that the eLog config file *is* updated and the logbook directory *is* created. So now I am trying to figure out how to debug this thing. Stefan, any clues?
|
|