Re: elogd runs by a user but not by root, posted by Dongwook Jang on Wed Apr 29 18:20:38 2009
|
Stefan Ritt wrote:
|
|
Re: elogd runs by a user but not by root, posted by Dongwook Jang on Thu Apr 30 20:49:03 2009
|
Stefan Ritt wrote:
|
Running ELOG as daemon in Windows not working, posted by Duarte Alexandre Vicente Pais on Fri Jan 31 18:22:50 2020
|
Hi, I tried to set up an ELOG from a windows machine. Its functionalities work without any problem, but I cannot access at all this ELOG from any other
machine. I tried to search in this forum, but with no avail.
Could someone perhaps tell me know how to fix this problem? Or did I miss something obvious in the configuration of the ELOG? |
|
Re: Running ELOG as daemon in Windows not working, posted by Duarte Alexandre Vicente Pais on Fri Jan 31 19:26:51 2020
|
Do you know which settings in the firewall panel I should change (windows 10 machine)? I went over all the access rules and could not find anything corresponding
to the ELOG.
Duarte |
Bug? Password file location changed, posted by David Spindler on Thu Nov 2 18:02:44 2006
|
I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my password to be invalid. I tried this on 2 machines
and same results. I did notice on the second one when I started it from a command prompt that it was creating a new empty password file in a different
location.
|
|
Re: Bug? Password file location changed, posted by David Spindler on Thu Nov 2 18:10:07 2006
|
[quote="David Spindler"]I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my password to be invalid.
I tried this on 2 machines and same results. I did notice on the second one when I started it from a command prompt that it was creating a new empty password
file in a different location.
|
|
Re: Bug? Password file location changed, posted by David Spindler on Fri Nov 3 14:40:36 2006
|
[quote="Steve Jones"][quote="David Spindler"][quote="David Spindler"]I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the
elog, it showed my password to be invalid. I tried this on 2 machines and same results. I did notice on the second one when I started it from a command
prompt that it was creating a new empty password file in a different location.
|
|
2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by David Spindler on Mon Nov 2 21:23:38 2009
|
I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that
it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations"
Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems |