ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68427
|
Wed Sep 21 17:23:15 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug fix | Linux | 3.0.0 | Re: notification error services in CentOS 6.5 | 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
|
|
|
|
68426
|
Sun Sep 18 03:31:42 2016 |
| Darren Hollinrake | hollinrakedp@gmail.com | Bug fix | Linux | 3.0.0 | Re: notification error services in CentOS 6.5 | 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
|
|
|
Attachment 1: elogd_modified
|
#!/bin/sh
# chkconfig: 3 90 10
# description: ELOG is a weblog with integrated database
# processname: elogd
# config: /usr/local/elog/elogd.cfg
# pidfile: /var/run/elogd.pid
# Source function library.
. /etc/rc.d/init.d/functions
# Check for the config file
if [ ! -f /usr/local/elog/elogd.cfg ]; then
exit 0
fi
# See how we were called.
case "$1" in
start)
if [ -f /var/run/elogd.pid ] ; then
pid=`cat /var/run/elogd.pid`
if [ -d /proc/$pid ] ; then
echo "elogd already running"
# echo_failure
exit 1
fi
fi
if [ -f /var/run/elogd.pid ] ; then
rm -f /var/lock/subsys/elogd
rm -f /var/run/elogd.pid
fi
echo -n "Starting elogd: "
/usr/local/sbin/elogd -D -c /usr/local/elog/elogd.cfg > /dev/null 2>&1
RETVAL=$?
if [ $RETVAL -eq 0 ] ; then
touch /var/lock/subsys/elogd
echo_success
else
echo_failure
fi
echo
;;
stop)
echo ""
if [ -f /var/run/elogd.pid ] ; then
echo -n "Stoping elogd: "
/bin/kill `cat /var/run/elogd.pid`
rm -f /var/lock/subsys/elogd
rm -f /var/run/elogd.pid
echo_success
echo
else
echo -n "No elogd running?"
echo
fi
;;
status)
status -p /var/run/elogd.pid /usr/local/sbin/elogd
RETVAL=$?
;;
restart|reload)
$0 stop
sleep 1
$0 start
;;
*)
echo "Usage: $0 {start|stop|status|restart}"
exit 1
esac
exit 0
|
68425
|
Mon Sep 12 19:10:03 2016 |
| Chris Smyth | chris.smyth@comcast.net | Question | Windows | ELOG V2.7.8-229 | Re: Body Width | > How do I make this section Wider or Shorter in the 2.7.8 version?
> Maybe I did something to make it shorter? ELCode shows as a full box but plain txt is very short box.
Never mind Found it
In Global set
Message Width = 95 |
68424
|
Mon Sep 12 18:44:09 2016 |
| Chris Smyth | chris.smyth@comcast.net | Question | Windows | ELOG V2.7.8-229 | Body Width | How do I make this section Wider or Shorter in the 2.7.8 version?
Maybe I did something to make it shorter? ELCode shows as a full box but plain txt is very short box. |
68423
|
Fri Sep 9 13:17:36 2016 |
| christian | c_grebing@web.de | Question | Windows | 3.1.2 | Re: Windows service settings | Hi Stefan,
you were right - running the service by an authorized user solved the problem.
Thanks a lot.
Cheers, Christian
Stefan Ritt wrote: |
These problems are usaully related to user rights. Try starting the service under a different (maybe admin) user.
Stefan
christian wrote: |
Hello,
I've been successfully using elog as a daemon since several years on a Linux machine. For some reasons recently I had to switch to a Windows 7 machine. Here, setting up the elog daemon doesn't work for me:
(a) running the command:
"...\ELOG\elog.exe" -c "...\ELOG\elogd.cfg"
in a windows shell works perfectly fine - logbook is up and running as set up in the cfg-file.
(b) However, starting the windows service manually (start->control panel->system and security->administrative tools->services) that was set up automatically during installation of elog leads to an error message:
"Error 1053: The service did not respond to the start or control request in a timely fashion"
From the service settings I can verify that the service is running exactly the same command that works in (a).
Could someone please share the windows service settings? Thanks in advance.
Cheers, Christian
|
|
|
68422
|
Fri Sep 9 11:33:04 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.1.2 | Re: Windows service settings | These problems are usaully related to user rights. Try starting the service under a different (maybe admin) user.
Stefan
christian wrote: |
Hello,
I've been successfully using elog as a daemon since several years on a Linux machine. For some reasons recently I had to switch to a Windows 7 machine. Here, setting up the elog daemon doesn't work for me:
(a) running the command:
"...\ELOG\elog.exe" -c "...\ELOG\elogd.cfg"
in a windows shell works perfectly fine - logbook is up and running as set up in the cfg-file.
(b) However, starting the windows service manually (start->control panel->system and security->administrative tools->services) that was set up automatically during installation of elog leads to an error message:
"Error 1053: The service did not respond to the start or control request in a timely fashion"
From the service settings I can verify that the service is running exactly the same command that works in (a).
Could someone please share the windows service settings? Thanks in advance.
Cheers, Christian
|
|
68421
|
Fri Sep 9 10:31:15 2016 |
| christian | c_grebing@web.de | Question | Windows | 3.1.2 | Windows service settings | Hello,
I've been successfully using elog as a daemon since several years on a Linux machine. For some reasons recently I had to switch to a Windows 7 machine. Here, setting up the elog daemon doesn't work for me:
(a) running the command:
"...\ELOG\elog.exe" -c "...\ELOG\elogd.cfg"
in a windows shell works perfectly fine - logbook is up and running as set up in the cfg-file.
(b) However, starting the windows service manually (start->control panel->system and security->administrative tools->services) that was set up automatically during installation of elog leads to an error message:
"Error 1053: The service did not respond to the start or control request in a timely fashion"
From the service settings I can verify that the service is running exactly the same command that works in (a).
Could someone please share the windows service settings? Thanks in advance.
Cheers, Christian |
68420
|
Tue Sep 6 22:18:29 2016 |
| Daniel Sajdyk | daniel.sajdyk@gmail.com | Question | Windows | 3.1.1-3f311c5 | Re: Highlight code? | Ok. Thanks a lot :)
Stefan Ritt wrote: |
In the HTML editor, you can select the code text, then select from the "Styles" drop-down the style "Computer Code", and on the "Normal" drop-down the formatting "Formatted". This puts the code in <pre> and <code> tags, so you don't have to manipulate HTML directly.
Daniel Sajdyk wrote: |
Looks like it works :)
Code need to be put in tags:
<pre><code class="sql">...</code></pre>
but it works.
Thank you :D
Best Regards
Daniel Sajdyk
Stefan Ritt wrote: |
I did not know about highlight.js . You can put it into any elog page with "Bottom text = ...". I tried it for this forum and put in some C code:
#include <stdio.h>
int main()
{
// printf() displays the string inside quotation
printf("C Programming");
return 0;
}
Seems like this works nicely. Thanks for that hint.
Daniel Sajdyk wrote: |
I thought so.
One more question :) I want manually add that parser (https://highlightjs.org), but I'm newby in that and don't know where ....
I know that downloaded hightlight pack I must put into folder scripts, but where to add this line:
<script>hljs.initHighlightingOnLoad();</script>
Stefan Ritt wrote: |
You can manually highlight code, but there is no automatic language parser.
Daniel Sajdyk wrote: |
Hello :)
Is there any way to highlight code (for example php, SQL) in elogs entries?
Best Regards
Daniel Sajdyk
|
|
|
|
|
|
|
|