Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 640 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 639, 640, 641 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  1788   Mon Apr 3 17:09:19 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportAll2.6.1-1668Re: elogd 2.6.1 program Crash is repeatable under Windows

Steve Jones wrote:
BTW, Stefan, unless you can make the most recent version of a Windows eLog available I cannot test the most recent -- I do not have access to a Windows development environment. Solaris-Yes, Linux-Yes, Windoze-No.


There is a 2.6.1-4 version for Windows for download, which contains the most recent code.
  1800   Fri Apr 7 05:07:20 2006 Reply Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1668Re: elogd 2.6.1 program Crash is repeatable under Windows

Stefan Ritt wrote:

Steve Jones wrote:
BTW, Stefan, unless you can make the most recent version of a Windows eLog available I cannot test the most recent -- I do not have access to a Windows development environment. Solaris-Yes, Linux-Yes, Windoze-No.


There is a 2.6.1-4 version for Windows for download, which contains the most recent code.



Quote:
Ok, I loaded the new Windows version ELOG V2.6.1-1681. The new version has the same behavior and it is entirely related to Top Group. With a simple Top Group setup things appear to work fine until one attempts to either create or delete a new logbook. There are other quirky things - I don't think Top Group is ready for really complex setups. In fact, this URL that is constructed by elog (http://localhost:8080/Engineering%20Compute%20Change%20Logs/Test/?cmd=Config) will cause elog to coredump but only with a very complex configfile. If I simply remove the "Top" from the "Group" directive I get the expected message "Error: logbook "Engineering Compute Change Logs" not defined in elogd.cfg
Please use your browser's back button to go back".

Another interesting point of reference - I went back to 2.5.9-4 (windows) and get the same behavior.

Now, making things really simple I added Top Group support to the demo that comes with the Windows install. This configfile:
[global]
port = 8080

Show top groups = 1
Top Group Demo Groups = demo, test7

[global Demo Groups]
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

[demo]

results in this redisplay after a new logbook create I have included in an attached screenshot. Please note that everything is generally not correct. So, even though eLog does not crash with this simple config it does support my observation that as I render the congfile more complex I corrupt eLog more until it finally crashes. Stefan, I would be interested in seeing how the above config runs on one of your windows systems.
Attachment 1: elog_2.JPG
elog_2.JPG
  1817   Thu May 4 16:01:29 2006 Question Tim Fowlertimfowler1@gmail.comBug reportWindows2.6.1-1681Elogd.exe crashes on windows
I have elog setup to send emails based on the priority of one of the attributes. When a new entry is created, the emails are sent successfully, however if the entry is edited or if you changed the attribute, elogd.exe will crash with a memory access error.

I have tried this and received the same results on different computers and different versions on Elog down to versions 2/6.0 beta 5. (it works correctly in that version).

The attribute in question is setup something like below:

Attributes = Ticket #, Site, Shift, Type, Area, System Name, Description, Priority, Status, Total Down Time, Last Revision

...(omitted config)

Options Priority = High, Medium, Low

...(omitted config)

Use Email Subject = $Site -- $System Name $Description
Use Email From = testuser@myexample.com

;Send email if priority is set to high
Email Priority High = testuser2@myexample.com

Display Email recipients = 1
Email Format = 14
  1841   Tue May 30 17:54:21 2006 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1681Losing field 'focus' when using Conditional Attributes
Stefan, any way to address this? It appears to only be applicable when one defines conditional Options - when javascript updates the conditional lists the input focus appears to shift to the HTML edit area. I am still running ELOG V2.6.1-1681 and this is under Windows (my test system).


With version 2.6.1 rev 1681 I believe this is when I started seeing the behavior such that when a conditional attribute value is selected the focus switches to the message entry window. It looks like when the javascript cond_submit() is called for some reason on returning focus defaults to the message window. This occurs under Windows (rev 1861) and Solaris (rev 1864). I can see in function chkform() that focus is returned for checking Required attributes, but I see nothing for conditional attributes.

Thanks
  1842   Tue May 30 17:57:46 2006 Reply Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1681Re: Losing field 'focus' when using Conditional Attributes

Steve Jones wrote:
Stefan, any way to address this? It appears to only be applicable when one defines conditional Options - when javascript updates the conditional lists the input focus appears to shift to the HTML edit area. I am still running ELOG V2.6.1-1681 and this is under Windows (my test system).


With version 2.6.1 rev 1681 I believe this is when I started seeing the behavior such that when a conditional attribute value is selected the focus switches to the message entry window. It looks like when the javascript cond_submit() is called for some reason on returning focus defaults to the message window. This occurs under Windows (rev 1861) and Solaris (rev 1864). I can see in function chkform() that focus is returned for checking Required attributes, but I see nothing for conditional attributes.

Thanks



Quote:
Attributes FunctionalArea, Operation, Category

#####################################################################################################
# Start defining how the form works
##################################################
# Define FunctionalArea
#
Options FunctionalArea = NFS{1}, LDAP{2}, LoadBalancer{3}, LSF{4}, SunRay{5}, Tarantella{6}, Vital Server{7}, ClearCase{8}, CFEngine{9}, DataCenter{10}, Compute{11}, Network{12}


##################################################
# Define Operation
#
{1} Options Operation = Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{2} Options Operation = Schema Change, Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{3} Options Operation = New Service Added, Configuration Change, Maintenance, SW Installation, SW Upgrade, Patch Applied
{4} Options Operation = Schema Change, Queue Change, License Change, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{5} Options Operation = Maintenance, SW Installation, SW Upgrade, Configuration Change, Firmware Upgrade, Patch Applied
{6} Options Operation = WebTop Change, Server Added, Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{7} Options Operation = New Service Added, Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{8} Options Operation = New VOB, New View, Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{9} Options Operation = SW Upgrade, Configuration Change, Patch Applied
{10} Options Operation = New HW Install, HW Maintenance, Power/UPS, HVAC, Network HW
{11} Options Operation = Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
{12} Options Operation = Maintenance, SW Installation, SW Upgrade, Configuration Change, Patch Applied
Tooltip FunctionalArea = The predefined Operations areas under which a Change may be scheduled.
Tooltip Operation = Choose FUNCTIONALAREA first

##################################################
# Define Category
#
{1} Options Category = HP, Celera, Sun, Brocade, StorageTek, EMC
{2} Options Category = Supplier, Hub, Consumer,Gateway, Client
{3} Options Category = F5, CSS
{4} Options Category = Master  
{5} Options Category = SunrayServer 
{6} Options Category = TTServer, DesktopServer
{7} Options Category = WWW, NIS, LISTSRV, NTP, DNS, MTA, TWIKI, ELOG, LOGGING HOST, GSH
{8} Options Category = VOB, VIEW
{9} Options Category = ?
{10} Options Category = Cisco, Netbotz, Liebert Paging
{11} Options Category = HPUX, Solaris, Linux
{12} Options Category = Cisco
Tooltip Category = Optional attribute. Please use for furthur classification.
  1846   Tue Jun 13 08:51:38 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportAll2.6.1-1681Re: Losing field 'focus' when using Conditional Attributes

Steve Jones wrote:
It appears to only be applicable when one defines conditional Options - when javascript updates the conditional lists the input focus appears to shift to the HTML edit area. I am still running ELOG V2.6.1-1681 and this is under Windows (my test system).


It was some new code used for inline images. If you upload an inline image, an extra window opens which lets you select the image file. After that operation, you want to have the focus back at the text box. Unfortunately this also happened now after the JavaScript update of conditional attributes. I fixed that in the new version 2.6.1-6.
  1847   Wed Jun 21 14:21:01 2006 Warning Ulrich Trüsselulrich.truessel@familienhund.chBug reportWindows2.6.1-6Corrupt page link
If a loggbook contains more than one page of entries, above and under the list are links for changing the page by number (or privous / last and all) conatining links looking like "http://localhost:8080/logbook/page2?mode=mode". This is the correct link and will work until Version 2.6.1-5!

In Version 2.6.1-6 the link is corrupted and look always like "http://localhost:8080/logbook/pag"
  1848   Wed Jun 21 17:03:23 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.6.1-6Re: Corrupt page link

Ulrich Trüssel wrote:
If a loggbook contains more than one page of entries, above and under the list are links for changing the page by number (or privous / last and all) conatining links looking like "http://localhost:8080/logbook/page2?mode=mode". This is the correct link and will work until Version 2.6.1-5!

In Version 2.6.1-6 the link is corrupted and look always like "http://localhost:8080/logbook/pag"


Well, in this forum the link is fine, so it must have to do with your special configuration. Can you try with the demo logbook and find out which configuration option causes this problem?
Goto page Previous  1, 2, 3 ... 639, 640, 641 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6