7 replies to this topic

[lmotu]

Hello all,

preliminary informations:

OS=windows XP
$U-Version=5.3.1


When I try to display the list of executions of a specific node, the buildup lasts about 10 minutes . Pressing "ESC"-Button
you will either see an uncompleted list or a completed list of executions, it depends on the time you will wait before pressing ESC.
Only my administrative client is affected. The other clients are working normally (max. 30 sec.)

I tried this with a long execution-list (6000 entries) and with short (80 entries). There is almost no difference between the holding times.

I checked the uniserve.log-file and saw a list of unreachable nodes. So I deleted this nodes from the "node" and "MU" definitions and from the "uxsrsrv.sck"-file.

After that I stopped $U, did a reorganisation and started $U.

Now, there are no more errors in the logs-files, this is the onliest success.

Trying to display the executions still lasts very long, but there are no errors listed in the logfiles.

There is another confusing situation:
Not all nodes are affected. There are nodes with much more entries than 6000 and the holding time for display the execution list is only half a minute at most.

I don't no what's wrong.

Thank you
lmotu

Edited by lmotu, 23 September 2009 - 08:24 AM.

[men]

Hello lmotu,

This type of problem is usually linked to:

- a misconfiguration of Dollar Universe "network" settings: Node list, MU list, file uxsrsrv.sck
- a network issue or misconfiguration

Can you check that:

- all your MUs are defined for Nodes that still exist. Update - or delete if you are absolutely sure you can do so - any MU that points to any undefined node

- all Nodes defined in the node table exist and are reachable over the network. Delete any node that would not exist over the network.

- all Nodes defined in the node table are also present in file uxsrsrv.sck

If you find any misconfiguration, after the updates, use the uxclenod tool to clean Dollar Universe data files (see the documentation to learn how to run this binary), then with the Company stopped, run an offline reorganization and restart the Company.

Also have your system/network administrators check that:

- DNS information is reliable and up-to-date (or hosts file or any similar mechanism your network may use)
- Time-out settings between the nodes.

If you don't find any thing which seems to explain the issue, you are left with opening a ticket at Dollar Access Technical support and provide them with an uxtrace with options c and s of both nodes.

Hope this helps,

Michel

[lmotu]

men, on September 23 2009, 08:48 AM, said:

Hello lmotu,

This type of problem is usually linked to:

- a misconfiguration of Dollar Universe "network" settings: Node list, MU list, file uxsrsrv.sck
- a network issue or misconfiguration

Can you check that:

- all your MUs are defined for Nodes that still exist. Update - or delete if you are absolutely sure you can do so - any MU that points to any undefined node

- all Nodes defined in the node table exist and are reachable over the network. Delete any node that would not exist over the network.

- all Nodes defined in the node table are also present in file uxsrsrv.sck

If you find any misconfiguration, after the updates, use the uxclenod tool to clean Dollar Universe data files (see the documentation to learn how to run this binary), then with the Company stopped, run an offline reorganization and restart the Company.

Also have your system/network administrators check that:

- DNS information is reliable and up-to-date (or hosts file or any similar mechanism your network may use)
- Time-out settings between the nodes.

If you don't find any thing which seems to explain the issue, you are left with opeing a ticket at Dollar Access Technical support and provide them with an uxtrace with options c and s of both nodes.

Hope this helps,

Michel

Hello Michel,

in the node- and MU-list there were some unknowns, I deleted (in the uxsrsrv.sck, too)
uxclennod <myAdminNode> returned following results:

Start purge on files x y

End of File U_FECLxx
Statistics:
Read U_FECL : 000000006
Erased U_FECL : 000000000
Read U_FECD : 000000000
Erased U_FECD : 000000000
Read U_FMEV : 000000004
Erased U_FMEV : 000000000

End purge on files x y


Then I shutdowned $U, and did a reorganisation
After startup $U there is no improvement.

I'll try to start an uxtrace.


Thank you
lmotu

Edited by lmotu, 24 September 2009 - 09:05 AM.

[men]

Hello again,

thank you for the update. Feel free to keep us posted when the isue has been analyzed by Dollar Access.

Have a nice day,

Michel

[lmotu]

here one more update:

I actually had no time to analyse the problem. (have a new burning $U-issue)
I let you know when I get the trace informations

please be patient

Greetings
lmotu

[men]

Hello,

Thanks for the update. No problem!

Michel

[lmotu]

men, on September 30 2009, 09:08 AM, said:

Hello,

Thanks for the update. No problem!

Michel

Hello Michel,

now we got new desktops and we did a new installation of the admin-clients. Now it works fine.
There must be a hardware problem

greetings
lmotu

[men]

Hello lmotu,

this is good news. Thank you for having kept us informed.

Michel