Author Topic: Mxe Ethernet problem?  (Read 2106 times)

Offline steve75

  • Jr. Member
  • **
  • Posts: 42
  • Country: it
  • Karma: +0/-0
    • View Profile
Mxe Ethernet problem?
« on: December 01, 2014, 09:54:45 AM »
Hi,
we have an Mxe with old release software MCD 4.0 SP4 with problem.
The system while running smoothly becomes unreachable. With Explorer and with telnet we don't have a way to connect it.
Only way to reconnect is a manual reboot.
After reboot all works fine.

Into log we see for a lot of times this record (category MSG)
MsSetLastError()->041 RC_MS_QUEUE_FULL     Message System queue is full     QueueName =Io2kMessage System queue is full
MsSetLastError()->027 RC_MS_ENQUEUE_ITEM_FAILED     Message System failed to append a message to its queue     QueueName =Io2kMessage System failed to append a message to its queue

And this log (category Call-Control)
DTRNKMON File Open Failure.  Context 10. File System Result: Device timeout           
DTRNKMON File Open Failure.  Context 20. File System Result: Device timeout       
DBMS - DBREFUTIL  Function : Save_Pages_On_FileOperation : End_Transaction     File : transientReturn Code : Device timeout

Any idea?
Thanks to all.
Stefano



Offline mszodiac

  • Sr. Member
  • ****
  • Posts: 232
  • Country: ca
  • Karma: +7/-0
    • View Profile
Re: Mxe Ethernet problem?
« Reply #1 on: December 01, 2014, 10:04:06 AM »
Have you done a dbms check full to see if there are any errors?

Offline pmhaynes

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 238
  • Country: gb
  • Karma: +11/-0
    • View Profile
Re: Mxe Ethernet problem?
« Reply #2 on: December 01, 2014, 10:09:18 AM »
"file system timeout"

only a guess but maybe change the hard drive

Offline steve75

  • Jr. Member
  • **
  • Posts: 42
  • Country: it
  • Karma: +0/-0
    • View Profile
Re: Mxe Ethernet problem?
« Reply #3 on: December 01, 2014, 10:20:32 AM »
Hi,
with DMBS CHECK FULL we don't see any problem:

DBMS info: Lab Default DB is off                                               
DBMS CHECK has commenced.                                                       
DBMS info: DBMS_INITIALIZED is on                                               
DBMS info: Journal is on                                                       
DBMS info: Debug is off                                                         
DBMS info: Cab: 20 Dim: 17 Traffic: 20                                         
DBMS info: DBMS CHECK scheduled for 2014-DEC-02 05:00:00.00 .                   
DBMS info: DBMS CHECK completed 2014-DEC-01 05:06:26.00 .                       
0 view error(s), 0 table error(s) detected.                                     
Machine Variant: IP                                                             
Installation ID: xxxxxxxxx                                                   
Time           : 2014-DEC-01 16:09:54.00    MON                                 
Plane          : A - active                                                     
File Redundancy: enabled                                                       
Mate Link      : manbusy                                                       
                                                                               
View:   1  cor               Tuples (Max):  32767   (Current):     64           
View:   2  cos               Tuples (Max):     96   (Current):     96           
View:   3  fac               Tuples (Max):  32767   (Current):    114
.....
.....
View: 192  vid_acdx_group_i  Tuples (Max):    999   (Current):      0           
View: 193  vid_acdx_group_d  Tuples (Max): 149850   (Current):      0           
Internal level audit starting.                                                 
DBMS info: DBMS CHECK completed 2014-DEC-01 16:18:03.00 .                       
Internal level audit finished successfully.                                     
0 view error(s), 0 table error(s) detected.


Thanks.
Stefano       

Offline mszodiac

  • Sr. Member
  • ****
  • Posts: 232
  • Country: ca
  • Karma: +7/-0
    • View Profile
Re: Mxe Ethernet problem?
« Reply #4 on: December 01, 2014, 01:05:05 PM »
@steve75

When you say unreachable, does this also mean the system does not respond to pings? Or do you just lose ESM (web interface) access?

You can try accessing the RTC shell (RAW, port 2002) and see if there's processes (ie. backup) that's holding up the ESM.


 

Sitemap 1 2 3 4 5 6 7 8 9 10