Re: notification error services in CentOS 6.5, posted by Darren Hollinrake on Sun Sep 18 03:31:42 2016 
|
The quick fix I found was to uncomment line 10 in the init.d file. (This was tested on a CentOS 6.8 AWS instance.)
. /etc/rc.d/init.d/functions
This will allow the status command to function properly.
Clean install:
[centos@ip-172-31-51-59 ~]$ service elogd status
status: invalid option: -p
After uncommenting line 10:
[centos@ip-172-31-51-59 ~]$ service elogd status
elogd (pid 11438) is running...
When you start elog it still won't show that the service started successfully (No 'OK'). If you go to stop the service, it will give you the proper 'OK' indicating it stopped successfully.
So to fix the missing 'OK' (or 'FAILED') we need to update the start section around line 51 as follows:
touch /var/lock/subsys/elogd
echo_success
else
echo_failure
fi
echo
;;
I've attached my modified init file which I believe corrects the above issues. I will say though that I'm not a programmer so I won't guarantee it's perfect. I haven't checked to see if CentOS 7 works with this modified version. Just checked it on a CentOS 7.2 AWS instance and it also appears to function correctly.
[root@oceana ~]# systemctl status elogd
● elogd.service - SYSV: ELOG is a weblog with integrated database
Loaded: loaded (/etc/rc.d/init.d/elogd)
Active: active (running) since Sun 2016-09-18 22:35:44 UTC; 7s ago
Docs: man:systemd-sysv-generator(8)
Process: 2263 ExecStop=/etc/rc.d/init.d/elogd stop (code=exited, status=0/SUCCESS)
Process: 2275 ExecStart=/etc/rc.d/init.d/elogd start (code=exited, status=0/SUCCESS)
Main PID: 2277 (elogd)
CGroup: /system.slice/elogd.service
└─2277 /usr/local/sbin/elogd -D -c /usr/local/elog/elogd.cfg
Sep 18 22:35:44 oceana elogd[2277]: elogd 3.1.1 built Aug 4 20...0
Sep 18 22:35:44 oceana elogd[2277]: revision
Sep 18 22:35:44 oceana elogd[2277]: Falling back to default gro..."
Sep 18 22:35:44 oceana elogd[2277]: Falling back to default use..."
Sep 18 22:35:44 oceana elogd[2277]: CKeditor detected
Sep 18 22:35:44 oceana systemd[1]: Started SYSV: ELOG is a webl....
Sep 18 22:35:44 oceana elogd[2279]: Falling back to default gro..."
Sep 18 22:35:44 oceana elogd[2279]: Falling back to default use..."
Sep 18 22:35:44 oceana elogd[2277]: ImageMagick detected
Sep 18 22:35:44 oceana elogd[2277]: SSLServer listening on port....
Hint: Some lines were ellipsized, use -l to show in full.
The old SysV style commands ('service elogd start|stop|status') also function correctly.
[root@oceana ~]# service elogd stop
Stopping elogd (via systemctl): [ OK ]
[root@oceana ~]# service elogd start
Starting elogd (via systemctl): [ OK ]
| Stefan Ritt wrote: |
|
The init script supplied with elog was originally written for Redhat. It seems like CentOS has slightly changed the init daemon management, but I'm not an expert on that, nor do I have CentOS installed. If somebody comes with a fixed elogd.init for CentOS, I'm happy to include that in the distribution.
/Stefan
| Banata wrote: |
|
hello, I just upgrade from 2.9 into 3.0.0 in CentOS 6.5
but after upgrade, I can't check elogd services via command line
service elogd status,
always result in missing argument, while it works with httpd or mysqld services and old elogd version.
I try to uninstall and install rom scratch and same result,
Okay I give you screenshoot of that,
you may notice, on check service status and stopping services, error resulted
|
|
|
Re: notification error services in CentOS 6.5, posted by Stefan Ritt on Wed Sep 21 17:23:15 2016
|
Ok, I will include this patch in the distribution.
Stefan
| Darren Hollinrake wrote: |
|
The quick fix I found was to uncomment line 10 in the init.d file. (This was tested on a CentOS 6.8 AWS instance.)
. /etc/rc.d/init.d/functions
This will allow the status command to function properly.
Clean install:
[centos@ip-172-31-51-59 ~]$ service elogd status
status: invalid option: -p
After uncommenting line 10:
[centos@ip-172-31-51-59 ~]$ service elogd status
elogd (pid 11438) is running...
When you start elog it still won't show that the service started successfully (No 'OK'). If you go to stop the service, it will give you the proper 'OK' indicating it stopped successfully.
So to fix the missing 'OK' (or 'FAILED') we need to update the start section around line 51 as follows:
touch /var/lock/subsys/elogd
echo_success
else
echo_failure
fi
echo
;;
I've attached my modified init file which I believe corrects the above issues. I will say though that I'm not a programmer so I won't guarantee it's perfect. I haven't checked to see if CentOS 7 works with this modified version. Just checked it on a CentOS 7.2 AWS instance and it also appears to function correctly.
[root@oceana ~]# systemctl status elogd
● elogd.service - SYSV: ELOG is a weblog with integrated database
Loaded: loaded (/etc/rc.d/init.d/elogd)
Active: active (running) since Sun 2016-09-18 22:35:44 UTC; 7s ago
Docs: man:systemd-sysv-generator(8)
Process: 2263 ExecStop=/etc/rc.d/init.d/elogd stop (code=exited, status=0/SUCCESS)
Process: 2275 ExecStart=/etc/rc.d/init.d/elogd start (code=exited, status=0/SUCCESS)
Main PID: 2277 (elogd)
CGroup: /system.slice/elogd.service
└─2277 /usr/local/sbin/elogd -D -c /usr/local/elog/elogd.cfg
Sep 18 22:35:44 oceana elogd[2277]: elogd 3.1.1 built Aug 4 20...0
Sep 18 22:35:44 oceana elogd[2277]: revision
Sep 18 22:35:44 oceana elogd[2277]: Falling back to default gro..."
Sep 18 22:35:44 oceana elogd[2277]: Falling back to default use..."
Sep 18 22:35:44 oceana elogd[2277]: CKeditor detected
Sep 18 22:35:44 oceana systemd[1]: Started SYSV: ELOG is a webl....
Sep 18 22:35:44 oceana elogd[2279]: Falling back to default gro..."
Sep 18 22:35:44 oceana elogd[2279]: Falling back to default use..."
Sep 18 22:35:44 oceana elogd[2277]: ImageMagick detected
Sep 18 22:35:44 oceana elogd[2277]: SSLServer listening on port....
Hint: Some lines were ellipsized, use -l to show in full.
The old SysV style commands ('service elogd start|stop|status') also function correctly.
[root@oceana ~]# service elogd stop
Stopping elogd (via systemctl): [ OK ]
[root@oceana ~]# service elogd start
Starting elogd (via systemctl): [ OK ]
| Stefan Ritt wrote: |
|
The init script supplied with elog was originally written for Redhat. It seems like CentOS has slightly changed the init daemon management, but I'm not an expert on that, nor do I have CentOS installed. If somebody comes with a fixed elogd.init for CentOS, I'm happy to include that in the distribution.
/Stefan
| Banata wrote: |
|
hello, I just upgrade from 2.9 into 3.0.0 in CentOS 6.5
but after upgrade, I can't check elogd services via command line
service elogd status,
always result in missing argument, while it works with httpd or mysqld services and old elogd version.
I try to uninstall and install rom scratch and same result,
Okay I give you screenshoot of that,
you may notice, on check service status and stopping services, error resulted
|
|
|
|
How do I use Preset Text only when a given topic is selected?, posted by Christina winson on Wed Sep 21 18:58:18 2016
|
Hi,
I'm looking to use a template for only a subset of logbook entries. Is there some way to apply a template when a specific topic or category is selected?
Help for the newbie much appreciated.
Christina |
|
Re: How do I use Preset Text only when a given topic is selected?, posted by Andreas Luedeke on Thu Sep 22 09:56:49 2016
|
Hi Christina,
You want to use "conditional attributes". See elog:68350 for an example. Cheers, Andreas
| Christina winson wrote: |
|
Hi,
I'm looking to use a template for only a subset of logbook entries. Is there some way to apply a template when a specific topic or category is selected?
Help for the newbie much appreciated.
Christina
|
|
|
Re: How do I use Preset Text only when a given topic is selected?, posted by Christina Swinson on Thu Sep 22 14:45:17 2016
|
Awesome! Thanks Andeas.
| Andreas Luedeke wrote: |
|
Hi Christina,
You want to use "conditional attributes". See elog:68350 for an example. Cheers, Andreas
| Christina winson wrote: |
|
Hi,
I'm looking to use a template for only a subset of logbook entries. Is there some way to apply a template when a specific topic or category is selected?
Help for the newbie much appreciated.
Christina
|
|
|
Using an RSS reader on a pasword protected elog, posted by Jackie Schwehr on Wed Sep 28 10:27:24 2016
|
I'm trying to set up a python rss parser to read the output from my collaboration's elog, however the elog is password protected and I cannot figure out how to have a python scrip get past the login screen. Is there something obvious I'm missing that will allow a parser to submit a username and password? If that's too python-specific of a question for this audience, then what is the exact security method elog uses, so I can get information on that? I've read through the documentation and either I don't know what I'm reading (likely) or I'm not looking in the right spot. |
|
Using an RSS reader on a pasword protected elog, posted by Jackie Schwehr on Wed Sep 28 10:36:53 2016
|
I'm trying to set up a python rss parser to read the output from my collaboration's elog, however the elog is password protected and I cannot figure out how to have a python scrip get past the login screen. Is there something obvious I'm missing that will allow a parser to submit a username and password? If that's too python-specific of a question for this audience, then what is the exact security method elog uses, so I can get information on that? I've read through the documentation and either I don't know what I'm reading (likely) or I'm not looking in the right spot. |
calculate diff of 2 date(s), posted by Alex Kühnel on Wed Sep 28 18:48:04 2016
|
hi
I have an elogsystem for documenting emergency services. I have a starttime and an endtime. Is it possible to calculate the diff between the 2 timestamps and convert it to minutes?
Attributes = Bereitschafts Kalender Woche, Bereitschafts Woche, Einsatzbeginn, Einsatzende, Einsatzzeit, Telefon Nummer, Station, Status, Problem
Options Status= Offen{1}, Erledigt{2}, Geschlossen{3}
......
Type Einsatzbeginn = datetime
Type Einsatzende = datetime
....
Subst Einsatzzeit = $shell(Einsatzende - Einsatzbeginn)
regards
/alex |
|