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

0000865: Ethernet connection NOT stable on IBM Server - MantisBT
MantisBT - Endian Firewall
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000865Endian FirewallHardware related (kernel, drivers, hardware)public2008-05-24 13:072009-10-27 12:02
Reportertethien 
Assigned Topeter-endian 
PrioritynormalSeveritycrashReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version2.2-rc1 
Target VersionFixed in Version2.3 
Customer Importance
Customer Occurrences
Queue
Summary0000865: Ethernet connection NOT stable on IBM Server
DescriptionI am testing Endian 2.2 rc1 on IBM xSeries 346 server.
The ethernet connection is NOT stable!!! It connect then disconnect all day.
I tested cable, other device ... all of it is OK.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Filestxt dmesg_out.txt (122,966) 2008-08-04 05:30
https://bugs.endian.com/file_download.php?file_id=167&type=bug
rar messages.rar (124,687) 2008-08-04 05:37
https://bugs.endian.com/file_download.php?file_id=168&type=bug
Issue History
Date ModifiedUsernameFieldChange
2008-05-24 13:07tethienNew Issue
2008-05-24 13:12tethienNote Added: 0001228
2008-05-24 13:13tethienNote Edited: 0001228
2008-05-26 13:17peter-endianNote Added: 0001230
2008-05-26 13:17peter-endianStatusnew => feedback
2008-05-27 09:22tethienNote Added: 0001234
2008-05-27 09:25tethienNote Edited: 0001234
2008-08-04 05:30tethienNote Added: 0001496
2008-08-04 05:30tethienFile Added: dmesg_out.txt
2008-08-04 05:37tethienFile Added: messages.rar
2008-08-19 14:23tethienStatusfeedback => closed
2008-08-19 14:23tethienResolutionopen => suspended
2008-09-09 11:09peter-endianNote Added: 0001587
2008-09-09 11:09peter-endianStatusclosed => feedback
2008-09-09 11:09peter-endianResolutionsuspended => reopened
2008-09-22 13:56tethienStatusfeedback => closed
2008-09-22 13:56tethienResolutionreopened => duplicate
2008-09-22 14:08tethienStatusclosed => feedback
2008-09-22 14:08tethienResolutionduplicate => reopened
2008-09-22 14:08tethienNote Added: 0001631
2008-09-22 16:10peter-endianNote Added: 0001633
2008-09-23 07:55tethienNote Added: 0001635
2008-09-23 10:23peter-endianNote Added: 0001637
2008-09-23 10:37peter-endianStatusfeedback => resolved
2008-09-23 10:37peter-endianFixed in Version => 2.3
2008-09-23 10:37peter-endianResolutionreopened => fixed
2008-09-23 10:37peter-endianAssigned To => peter-endian
2009-10-27 12:02peter-endianStatusresolved => closed

Notes
(0001228)
tethien   
2008-05-24 13:12   
(edited on: 2008-05-24 13:13)
Endian 2.2 beta 3 not have this bug. It run well on this server.
I not install endian 2.2 beta 4.
(0001230)
peter-endian   
2008-05-26 13:17   
Can you please send us the output of

dmesg

and check in /var/log/messages if you see something suspect before the reboot?
(0001234)
tethien   
2008-05-27 09:22   
(edited on: 2008-05-27 09:25)
I am very sorry. I rollbacked to 2.2 beta 3.
I not saved any log file.
(0001496)
tethien   
2008-08-04 05:30   
I am testing v2.2 RC2 and this bug repeated.
(0001587)
peter-endian   
2008-09-09 11:09   
if you mean that the uplink is not stable, that's because of a configuration problem:
"pppd[16776]: In file /etc/ppp/peers/main: unrecognized option 'Pro'"

Don't know where this "Pro" comes from. But this hinders the uplink from connecting. The uplinksdaemon constantly tries to connect, therefore the ethernet link goes up and down all the time.
(0001631)
tethien   
2008-09-22 14:08   
The "Pro" come from "Service:" value on Step 4/7 on Network setup wizard.
This value is "Mega Pro" !!!.
(0001633)
peter-endian   
2008-09-22 16:10   
can you try to edit this file:
nano /usr/lib/uplinks/generic/pppoe.sh

search for "SERVICENAME"

and change this:
       echo "rp_pppoe_service $SERVICENAME" >> $PEERFILE
in that:
       echo "rp_pppoe_service \"$SERVICENAME\"" >> $PEERFILE

afterwards, the service name should be written down into the configuration file quoted with "".
(0001635)
tethien   
2008-09-23 07:55   
OK.
After change /usr/lib/uplinks/generic/pppoe.sh file, edit Uplink, save, Uplink connection connected successfully.
(0001637)
peter-endian   
2008-09-23 10:23   
great. i will integrate it