Hello List,
Unfortunately there was no response on my former E-mail on this issue.
The issue is: Two sunrays behind a NAT router are interfering, which
makes this setup unusable for production sites.
In the mean time we have upgraded some things:
1. Solaris is nowversion: 01/06
2. SRSS is now upgraded to: 3.1 patch 120879-03
3. SRSS server in now on a public ip address ( server on pulic ip ---->
internet -----> NAT -----> Sunrays on private ip)
But the problem still remains.
Can any one of the Sun guys (are there girls?) please give me some
feedback on this?
Kind regards,
Ivar Janmaat
/var/adm/messages:
Jul 6 09:41:32 server12 utsessiond[2011]: [ID 515966 daemon.warning]
double mapping:
Jul 6 09:41:32 server12 utsessiond[2011]: [ID 521955 daemon.warning]
oldSession 0x196018
Jul 6 09:41:32 server12 utsessiond[2011]: [ID 307879 daemon.warning]
newSession 0x196128 (EMPTY)
Jul 6 09:41:32 server12 utsessiond[2011]: [ID 747569 daemon.warning]
Old connect made 1970.007 seconds ago
Jul 6 09:41:32 server12 utdevmgrd[1990]: [ID 515966 daemon.warning]
double mapping:
Jul 6 09:41:32 server12 utdevmgrd[1990]: [ID 676677 daemon.warning]
oldSession 0x2561a8 ip 62.163.103.22
Jul 6 09:41:32 server12 utdevmgrd[1990]: [ID 436761 daemon.warning]
newSession 0x25b9b0 ip 62.163.103.22
Jul 6 09:41:32 server12 utdevmgrd[1990]: [ID 747569 daemon.warning]
Old connect made 1970.001 seconds ago
This is the error we are seeing in the logfiles after the second sunray
is turned on behind NAT.
Ivar Janmaat wrote:
Hello,
I am feeling a bit sorry for the other user on one of our sunray
locations.
Everytime I come in and put the power on my sunray he has to reboot
his sunray because it is "hanging".
After he has rebooted his sunray, everything is working again and we
can work together without any problem.
Below is the output from /var/adm/messages
Setup:
Sunray 3.1, Solaris 3/05
Server is on private ip ---- NAT -----Internet ------NAT -------Sunray
is on private ip.
Dec 22 12:22:08 jumper1 utsessiond[2939]: [ID 515966 daemon.warning]
double mapping:
Dec 22 12:22:08 jumper1 utsessiond[2939]: [ID 521955
daemon.warning] oldSession 0x197318
Dec 22 12:22:08 jumper1 utsessiond[2939]: [ID 307879
daemon.warning] newSession 0x197928 (EMPTY)
Dec 22 12:22:08 jumper1 utsessiond[2939]: [ID 747569
daemon.warning] Old connect made 14662.478 seconds ago
Dec 22 12:22:08 jumper1 utdevmgrd[2955]: [ID 515966 daemon.warning]
double mapping:
Dec 22 12:22:08 jumper1 utdevmgrd[2955]: [ID 676677
daemon.warning] oldSession 0x2573b0 ip 62.163.103.22
Dec 22 12:22:08 jumper1 utdevmgrd[2955]: [ID 436761
daemon.warning] newSession 0x25e6d0 ip 62.163.103.22
Dec 22 12:22:08 jumper1 utdevmgrd[2955]: [ID 747569
daemon.warning] Old connect made 14662.483 seconds ago
Dec 22 12:22:52 jumper1 utdevmgrd[2955]: [ID 515966 daemon.warning]
double mapping:
Dec 22 12:22:52 jumper1 utdevmgrd[2955]: [ID 676677
daemon.warning] oldSession 0x2573b0 ip 62.163.103.22
It looks like the Sunray server is restoring the session from when I
switched of my Sunray but it disconnects the other sunray on our
location in the proces.
Is this a known bug?
Ivar
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
