Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon12.gif   Elog 2.3.3, problems of 2.3.2 only partly solved, posted by djek on Thu Mar 20 21:07:09 2003 
    icon2.gif   Re: Elog 2.3.3, problems of 2.3.2 only partly solved, posted by Stefan Ritt on Thu Mar 20 21:07:09 2003 
       icon2.gif   Re: Elog 2.3.3, problems of 2.3.2 solved, posted by djek on Thu Mar 20 21:07:09 2003 
Message ID: 255     Entry time: Thu Mar 20 21:07:09 2003     In reply to: 254
Icon: Reply  Author: djek  Author Email: djek@nospam.invalid 
Category: Bug report  OS:   ELOG Version:  
Subject: Re: Elog 2.3.3, problems of 2.3.2 solved 
> > After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
> > as stylesheets, images or passwordfiles.
> > 
> > Cannot open file /usr/local/elogdata/logbooks/djeks/password!
> 
> If you installed from the RPM, elogd runs under the user "elog". If you have 
> installed a previous version under a different user, it might be that elogd 
> does not have read or write access to it. A 
> 
> "chown -R elog.elog /usr/local/elogdata"
> 
> might help.
>
 
It did, a lot, guess I missed that one in the changelog.

Had some trouble with subdir too:
changed it to its full path
restarted elogd
worked

As a test I changed subdir to it's relative path
restarted
It kept working

mmmm, I wonder where that twighlight tune comes from ...
ELOG V3.1.5-3fb85fa6