ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 173 of 806

Not logged in

Find | Login | Help

New entries since:

Thu Jan 1 01:00:00 1970

Full | Summary | Threaded | Hide attachments

6445 Entries

Goto page Previous 1, 2, 3 ... 172, 173, 174 ... 804, 805, 806 Next

Wed Sep 28 10:36:53 2016

Jackie Schwehr

jackie.schwehr@colostat.edu

Question

Linux

ELOG V2.9.2-245

Using an RSS reader on a pasword protected elog

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.

Draft

Wed Sep 28 10:27:24 2016

Jackie Schwehr

jackie.schwehr@colostat.edu

Question

Linux

ELOG V2.9.2-245

Using an RSS reader on a pasword protected elog

68431

Fri Sep 23 23:38:28 2016

Matthew Sauder

matthew.sauder@saskcancer.ca

Question

Windows

3.1.0-c701f01

Re: FCKEditor not working correctly on a Windows server.

I know I'm a little late but is there a way to do this from elog? I've tried using the following line in the config but it doesn't seem to work in IE10. I figure if there is a way to modify the <head> before the page loads there could be hope.

Top text = <script>var meta = document.createElement('meta');meta.httpEquiv = "X-UA-Compatible";meta.content = "IE=edge";var head = document.getElementsByTagName('head')[0];head.insertBefore(meta, head.firstChild);</script>

Richard Stamper wrote:

If you are using IE as your browser, the problem may be with that rather than the server. By default IE 11 display intranet sites in a "Compatibility mode" which breaks the FCKEditor in Elog version 3. Fortunately this mode can be disabled, which is what I have had to advise users here to do.

Click on the "cogwheel" and select "Compatibility settings"
Deselect "Display intranet sites in Compatibility view"

Pictures attached

Marty Jansen wrote:

Sorry for the late reply. I have installed a slightly newer version of Elog, but the results are the same. I do get de the 3 editor bars, but the top 2 are greyed out and the bottom one doesn't do anything if clicked. I have commented out the lines that refer to the online equation editor, but that doesn't help much either. I think I let it rest. The old 2.9.xx version still works great, so we leave it at that.

Thanks anyway for the suggestions

Marty

Marty Jansen wrote:

Hi,

After working many years with previous versions of ELOG, I decided to update to the latest version.
I have installed ELOG version 3.1.0 on a WIndows 2012R2 server with IE 1. The editor is showing up, but everything is greyed out, execpt for some items on the bottom row. (Style, Lettertype...) and after I do load a preset text form with different colors, the page remains white. The tables and text in the form is showing up.

The previous version with the older editor was working great on the same server.

Any suggestions?

68430

Thu Sep 22 14:45:17 2016

Re: How do I use Preset Text only when a given topic is selected?

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

68429

Thu Sep 22 09:56:49 2016

Andreas Luedeke

andreas.luedeke@psi.ch

Question

Linux

3.1.1

Re: How do I use Preset Text only when a given topic is selected?

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

68428

Wed Sep 21 18:58:18 2016

How do I use Preset Text only when a given topic is selected?

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

68427

Wed Sep 21 17:23:15 2016

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
;;

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:

/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

Goto page Previous 1, 2, 3 ... 172, 173, 174 ... 804, 805, 806 Next

ELOG V3.1.5-3fb85fa6