SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264
|
Notes |
|
|
(0003769)
|
|
aender
|
|
2010-02-11 18:37
|
|
Sorry.
This only happens at applying Profile settings. |
|
|
|
|
does not happen to me
what means is stuck? is the notification messages not going away leaving you in a situation where you can't klick any link?
or is the browser not reacting?
does it happen also with firefox? |
|
|
|
(0003950)
|
|
aender
|
|
2010-03-05 13:38
|
|
Hmm..
Can´t reproduce this. Maybe the last efw-proxy package from yesterday solves this issue.
So please close this bug. |
|
|
|
|
I'm not sure what aender is getting at, but I've had problems configuring EFW from Safari in the past, worked fine when I use basically any other browser.
For me, it's basically impossible to configure almost everything from Safari. For example, I can start/stop the proxy, but I can't change any of the settings. I can also completely configure QoS, but I can't touch port forwarding.
I get the following when I'm trying to save proxy settings in Safari:
Safari can’t open the page “https://10.0.0.1:10443/cgi-bin/proxyconfig.cgi [^]” because the server where this page is located isn’t responding. |
|
|
|
|
Can reproduce from here, too. I'm able to apply settings from Safari, but after 15 seconds my browser completely freezes.
It also gets stuck from FireFox in Mac OS X, but it does not freeze the browser, so I'm able to call the dashboard again by changing the URL in the browser.
The changes are applied, the browser window basically just does not get un-grayed.. |
|
|
|
(0005032)
|
|
compdoc
|
2010-11-07 14:15
(edited on: 2010-11-07 14:16) |
|
I have two efw firewalls. One that was version 2.4 that I upgraded to 2.4.1 with the efw-upgrade command, and one that was version 2.2 that I tried to upgrade to 2.4.1 with efw-upgrade, but which failed so I had to install 2.4 from scratch and then upgrade to 2.4.1.
Anyway, both are now getting stuck on this "Proxy settings are being applied. Please hold..." page. Doesn't matter if I use IE or Firefox, and it doesnt matter which computer I use...
|
|
|
|
(0005033)
|
|
volga629
|
2010-11-07 15:29
(edited on: 2010-11-07 15:43) |
|
Peter please read my report about emi I think this is cause the problem.
I have the same issue any service cannot be reloaded through web GUI.
my ticket 0003262
Here again log from /var/log/emi
Nov 7 10:23:52 emi[5843]: Failed calling status display 'status.notifications.services'.
Nov 7 10:23:52 emi[5843]: Failed calling status display 'status.notifications.services'.
Nov 7 10:23:55 emi[5843]: Failed calling status display 'status.notifications.services'.
Nov 7 10:23:55 emi[5843]: Failed calling status display 'status.notifications.services'.
Nov 7 10:23:56 emi[5843]: Failed calling status display 'status.notifications.services'.
Nov 7 10:23:57 emi[5843]: Failed calling status display 'status.notifications.services'.
Nov 7 10:23:58 emi[5843]: Failed calling status display 'status.notifications.services'.
Nov 7 10:23:58 emi[5843]: Failed calling status display 'status.notifications.services'.
Nov 7 10:23:59 emi[5843]: Failed calling status display 'status.notifications.services'.
Nov 7 10:23:59 emi[5843]: Failed calling status display 'status.notifications.services'.
Nov 7 10:24:00 emi[5843]: Failed calling status display 'status.notifications.services'.
Nov 7 10:24:00 emi[5843]: Failed calling status display 'status.notifications.services'.
Nov 7 10:24:01 emi[5843]: Failed calling status display 'status.notifications.services'.
Nov 7 10:24:02 emi[5843]: Failed calling status display 'status.notifications.services'.
Nov 7 10:24:02 emi[5843]: Failed calling status display 'status.notifications.services'.
|
|
|
|
|
|
I verified the stuck with one system when applying the firewall rules, after I added a port forwarding & Applying the rule, the "apply" keep showing. |
|
|
|
|
Veirified also with another system when applying the routing rules.
The "apply" keeps popping up. |
|
|
|
|
Applied the latest updates to ver. 4.1 today 2010-11-14 and the problem still exist. This is from /var/log/emi before and after the update:
Nov 14 10:34:16 endian emi[5119]: Failed calling status display 'status.notifications.services'.
Nov 14 10:36:25 endian emi[5119]: Call 'commands.migration.update({})'
Nov 14 10:36:28 endian emi[5119]: Packages list updated
Nov 14 10:37:18 endian emi[5119]: Failed calling status display 'status.notifications.services'.
Nov 14 10:40:29 endian emi[5119]: Call 'commands.migration.run({'release': u'1.endian8', 'epoch': u'1', 'version': u'2.4.7', 'pkg': u'efw-proxy'})'
Nov 14 10:40:29 endian emi[5119]: Migrate package 'efw-proxy' to version '{'release': '1.endian8', 'epoch': '1', 'version': '2.4.7'}'
Nov 14 10:40:30 endian emi[5119]: Call 'commands.emi.reload({'module': u'proxy'})'
Nov 14 10:40:30 endian emi[5119]: Reload EMI...
Nov 14 10:40:31 endian emi[5119]: Initializing status subsystems of EMI modules in '/usr/lib/python2.4/site-packages/endian'
Nov 14 10:40:31 endian emi[5119]: Initialized status subsystem of module: collectd
Nov 14 10:40:31 endian emi[5119]: Initialized status subsystem of module: networkstatus
Nov 14 10:40:31 endian emi[5119]: Load test status subsystem of module 'status'
Nov 14 10:40:31 endian emi[5119]: Load services notifications status interface
Nov 14 10:40:31 endian emi[5119]: Initialized status subsystem of module: status
Nov 14 10:40:32 endian emi[5119]: Initialized status subsystem of module: uplinksdaemon
Nov 14 10:40:32 endian emi[5119]: Initializing web subsystems of EMI modules in '/usr/lib/python2.4/site-packages/endian'
Nov 14 10:40:32 endian emi[5119]: Initialized web subsystem of module: commands
Nov 14 10:40:32 endian emi[5119]: Initialized web subsystem of module: firewallgui
Nov 14 10:40:32 endian emi[5119]: Initialized web subsystem of module: ips
Nov 14 10:40:32 endian emi[5119]: could not import smsnotifications
Nov 14 10:40:32 endian emi[5119]: Initialized web subsystem of module: notifications
Nov 14 10:40:32 endian emi[5119]: Initialized web subsystem of module: proxy
Nov 14 10:40:32 endian emi[5119]: Initialized web subsystem of module: qos
Nov 14 10:40:32 endian emi[5119]: Initialized web subsystem of module: status
Nov 14 10:40:33 endian emi[5119]: Initialized web subsystem of module: webshell
Nov 14 10:41:01 endian emi[5119]: Call 'commands.migration.run({})'
Nov 14 10:50:17 endian emi[5119]: Failed calling status display 'status.notifications.services'.
Nov 14 10:52:10 endian emi[5093]: Initializing status subsystems of EMI modules in '/usr/lib/python2.4/site-packages/endian'
Nov 14 10:52:10 endian emi[5093]: Initialized status subsystem of module: collectd
Nov 14 10:52:10 endian emi[5093]: Initialized status subsystem of module: networkstatus
Nov 14 10:52:10 endian emi[5093]: Load test status subsystem of module 'status'
Nov 14 10:52:10 endian emi[5093]: Load services notifications status interface
Nov 14 10:52:10 endian emi[5093]: Initialized status subsystem of module: status
Nov 14 10:52:11 endian emi[5093]: Initialized status subsystem of module: uplinksdaemon
Nov 14 10:52:11 endian emi[5093]: Initializing web subsystems of EMI modules in '/usr/lib/python2.4/site-packages/endian'
Nov 14 10:52:11 endian emi[5093]: Initialized web subsystem of module: commands
Nov 14 10:52:11 endian emi[5093]: Initialized web subsystem of module: firewallgui
Nov 14 10:52:11 endian emi[5093]: Initialized web subsystem of module: ips
Nov 14 10:52:12 endian emi[5093]: could not import smsnotifications
Nov 14 10:52:12 endian emi[5093]: Initialized web subsystem of module: notifications
Nov 14 10:52:12 endian emi[5093]: Initialized web subsystem of module: proxy
Nov 14 10:52:12 endian emi[5093]: Initialized web subsystem of module: qos
Nov 14 10:52:12 endian emi[5093]: Initialized web subsystem of module: status
Nov 14 10:52:13 endian emi[5093]: Initialized web subsystem of module: webshell
Nov 14 11:11:22 endian emi[5093]: Failed calling status display 'status.notifications.services'.
Nov 14 11:12:49 endian emi[5093]: Call 'commands.migration.update({})'
Nov 14 11:12:53 endian emi[5093]: Packages list updated
Nov 14 11:12:58 endian emi[5093]: Call 'commands.migration.run({})'
Nov 14 11:13:30 endian emi[5093]: Failed calling status display 'status.notifications.services'.
Nov 14 11:31:08 endian emi[5093]: Failed calling status display 'status.notifications.services'. |
|
|
|
|
Verified with the last updates with
- Internet Explorer
- Safari
- Firefox
- Opera
The bug is confirmed and not related to the browsed used.
Lo |
|
|
|
(0005167)
|
|
baldy
|
|
2010-11-20 08:58
|
|
|
Using Chrome the message is stuck at Writing Sarg configuration. Refreshing the page shows settings applied properly. |
|
|
|
|
|
Issue confirmed also with 2.4 enterprise. |
|
|
|
|
There is a bug in this file /home/httpd/html/include/servicesubscriber.js ca. at line 699.
Please move the first function into the body of the second.
Before:
/* Define the poll function */
pollfn = lazy_apply(function() {
/* Only allow one request at a time */
if(this.requestInProgress) {
return;
}
this.requestInProgress = true;
/* Fire a new request to the notification location */
__lastXHR = $.getJSON(this.status_location + '&rand=' + rand(),
lazy_apply(this.onSuccess, this),
lazy_apply(this.onError, this))
}, this);
/* Call pollfn using interval as interval */
var starter = lazy_apply(function() {
/* A state different from initiating implies, that the subscription
* was aborted already. This might happen, if a subscription is
* controlled by a master.
*/
if(this.state != 'INITIATING') return;
/* Check if the service has already died with an error */
if(this.type != 'observe')
this.serviceEndedAlready();
/* Call once immediately, then after the defined interval */
interval=2000;
this._interval_obj = setInterval(pollfn, interval);
}, this);
after:
/* Call pollfn using interval as interval */
var starter = lazy_apply(function() {
/* Define the poll function */
pollfn = lazy_apply(function() {
/* Only allow one request at a time */
if(this.requestInProgress) {
return;
}
this.requestInProgress = true;
/* Fire a new request to the notification location */
__lastXHR = $.getJSON(this.status_location + '&rand=' + rand(),
lazy_apply(this.onSuccess, this),
lazy_apply(this.onError, this))
}, this);
/* A state different from initiating implies, that the subscription
* was aborted already. This might happen, if a subscription is
* controlled by a master.
*/
if(this.state != 'INITIATING') return;
/* Check if the service has already died with an error */
if(this.type != 'observe')
this.serviceEndedAlready();
/* Call once immediately, then after the defined interval */
pollfn();
interval=2000;
this._interval_obj = setInterval(pollfn, interval);
}, this); |
|
|
|
|
Apparently, this issue still exists. I have downloaded a new iso and installed 2.4.1 and re installed the software. Processing hangs regardless of if I am applying settings via the Intrusion Protection System or Proxy Setting. This was not a issue with 2.4.
Hardware used:
Dell Optiplex 755
Dual Core Processor
4GB Memory
500 Gb Hard Drive
The work around is to refresh screen and go back 1 page if using the web interface.
Out of curiosity, is this issue also present via the CLI?
Thanks, |
|
|
|
|
I tested today after replacement of code, but problem still exist on attempt of Snort restart.
Nov 25 22:46:06 wall emi[29873]: Failed calling status display 'status.notifications.services'.
Nov 25 22:55:01 wall emi[29873]: Failed calling status display 'status.notifications.services'.
Nov 25 22:55:12 wall emi[29873]: Failed calling status display 'status.notifications.services'. |
|
|
|
|
|
I freshly install 2.4.1 and getting same issue. |
|
|
|
|
|
Guys, please let us know when you release the patch on EN. |
|
|
|
|
Hi guys.
Sorry, I haven't noticed the logging message.
I'm right intending that the js notifaction disappears with the first bugfix?
To fix the problem with the logging please replace this if in the file /usr/lib/python2.4/site-packages/endian/status/notification.py ca at line:
if not os.path.exists(filename):
raise NotFoundError("Status file for service '%s' not found." % service)
with this one:
if not os.path.exists(filename):
debug("Status file for service '%s' not found." % service)
return {
"exception": "Status file for service '%s' not found." % service,
"error": "Status file for service '%s' not found." % service
}
The first fix is still necassary! |
|
|
|
(0005253)
|
|
NarinNil
|
2010-11-30 09:54
(edited on: 2010-11-30 09:55) |
|
Hi max
1. i found below function at line 1267 not 699
/* Define the poll function */
pollfn = lazy_apply(function() {
/* Only allow one request at a time */
if(this.requestInProgress) {
return;
...
2. file /usr/lib/python2.4/site-packages/endian/status/notification.py
not found on my system only have similar files = notifications.pyc
and content files not same as your post (size 2,458 bytes)
of course i try both solution but still got this issue, any idea ?
my system = 2.4.1 Kernel 2.6.32.24-57.e38.i586
|
|
|
|
|
Hi
Sorry, my servicesubscriber.js file has only 1269 lines. :)
And I forget that on the iso are not all .py files, because of the space...
I have uploaded the both fixed files, so you can replace/insert them on your system(I have taken the files from a 2.4.1 community! but it should work on every 2.4):
The location on the fw of notifications.py is(above I forget the 's'):
/usr/lib/python2.4/site-packages/endian/status/notifications.py
The location on the fw of servicesubscriber.js is:
/home/httpd/html/include/servicesubscriber.js
Please mind that you must reload the proxypage to update the js files in the cache of your browser and you must restart emi ('/etc/init.d/emi restart'), otherwise the changes will not have any effect. |
|
|
|
(0005256)
|
|
NarinNil
|
2010-11-30 11:09
(edited on: 2010-11-30 11:42) |
|
Thanks max
i will try and then feedback again ;)
---------------------------------------------------------
OK It's wokr thank many time max :D
|
|
|
|
|
That's fine.
Thank you for your feedback! |
|
|
|
|
|
Any way to have this bug fixed with an official update (efw-upgrade) ? itìs a quite serious bug, since a core feature is not properly working. |
|
|
|
|
|
Yes, there will be an upgrade. |
|
|
|
|
Max is there any sort of eta on the revised iso or upgrade?
Thank you... |
|
|
|
|
Hi
Sorry, the release date for updates is not decided yet, it may takes 2-3 weeks. But I think in month sure. |
|
|
|
|
I tried replacing the attached files but it doesn't resolve the issue. A by product of replacing the files is that the "switches" in the gui doesn't work after. Ex. Cannot turn the proxy ON or OFF.
Using the latest community edition from the website. 2.4.1 |
|
|
|
(0007262)
|
|
cemendes
|
2011-08-03 22:03
(edited on: 2011-08-04 14:15) |
|
I applied the files attached to this bug and they worked! However, I think the file name notifcations.py is misspelled. Would the correct name be notifications.pyc? The reason I ask is that there is a notifcations.pyc already in that directory.
Again, ANY ETA for a formal release?
|
|
|
|
|
What is the correct file extension? PYC or PY
All of the other files in that location are PYC |
|
|
|
(0007401)
|
|
baldy
|
|
2011-09-12 07:11
|
|
Just copy them in as is.
No need to change the extension.
Reboot when done.
Regards,
Klaas-Jan |
|
|
|
(0007866)
|
|
rosch
|
|
2012-05-12 16:42
|
|
Doesn't work for me, the page is still stuck even after a reboot.
Has there ever been a efw-update?
thanks for looking into this. |
|
|
|
(0007909)
|
|
endiqw
|
|
2012-06-12 08:07
|
|
|
I have fun read this blog post. I want to see more about this topic.Thank you for publishing this quality information.I have bookmarked this web page and can appear again following several days to verify for virtually any new posts that you simply make.And are you interested in understanding my website?Please http://www.airmax-2012.com/women-air-max-classic-bw-c-125.html. [^] |
|
|
|
(0008351)
|
|
p1000
|
|
2012-12-10 09:16
|
|
We are having similar problem in version 2.5.1.
The servicesubscriber.js file is the same no changes.
However for notification.py, I can't find it at /usr/lib/python2.4/site-packages/endian/status/ only notification.pyc. After copy the file over and rebooted, the applying popup message did not appear anymore.
Is this suppose to be the permanent fixed ? |
|
notifications.py (3,949) 2010-11-30 10:34