Client Server connection problem

This is for the remaining stuff.

Moderator: sepma

ian
Posts: 15
Joined: September 4th, 2009, 5:36 am
Spam Stop: No
SEP sesam: Software

Client Server connection problem

Post by ian » September 4th, 2009, 7:02 am

I'm trying to install SESAM on a couple of servers to try it out. One server is a SLES10SP2 server which I've installed SESAM Server onto (sesam_srv-3.4.1-67.sles10.i586.rpm). This server has a tape drive on it & it seems to be working correctly. This server is called testsserv.

Next I installed SESAM client (sesam_cli-3.4.1-67.sles10.i586.rpm) onto a second server running OES2 Linux. This server is called hamfp01v

Both servers are registered in my DNS server (forward & reverse lookup).

The firewall is disabled on both servers!

On the first server, I ran /opt/sesam/bin/sesam/sm_ctrlc -l root hamfp01v sbc (hamfp01v is the name of the second server) & it came back with:
Error: Network communication problem: CTRLD reply: 2009-09-04 08:28:08: scd-1136: Error: Host [testserv.domain.com] is not allowed to connect or security problem for user: [root].

Then I ran /opt/sesam/bin/sesam/sm_setup set_client testserv on the second server to allow it to connect with testserv
Now when I run /opt/sesam/bin/sesam/sm_ctrlc -l root hamfp01v sbc, I get:
Error: Network communication problem: STDLIB error: 11 - Resource temporarily unavailable. accept() call timed out probably due to a Firewall.

As I said, the firewall is disabled on both servers. The second server (hamfp01v) is a XEN virtual machine, so I'm not sure if that is causing the problem, but the firewall on the XEN host is also disabled. I don't know what else to try!

ossi1001
Posts: 77
Joined: May 15th, 2009, 10:41 am

Re: Client Server connection problem

Post by ossi1001 » September 4th, 2009, 11:36 am

Hy,

I would recommend to execute this command
/opt/sesam/bin/sesam/sm_setup set_client testserv.domain.com

because your first command shows, the host with the fqdn is not allowed to connect.

Further you can try to add the parameter to use single port connection from server to client:
/opt/sesam/bin/sesam/sm_ctrlc -l root -s hamfp01v sbc

If just the parameter -s works, you have to add this parameter in your Sesam GUI. When editing or adding a new client, you can choose the tab "Options" and there you have to type -s in the access options.

Regards, Florian

ian
Posts: 15
Joined: September 4th, 2009, 5:36 am
Spam Stop: No
SEP sesam: Software

Re: Client Server connection problem

Post by ian » September 8th, 2009, 3:39 am

Thanks, that seems to have sorted it out now.

Cheers,
ian

ian
Posts: 15
Joined: September 4th, 2009, 5:36 am
Spam Stop: No
SEP sesam: Software

Re: Client Server connection problem

Post by ian » September 10th, 2009, 7:19 am

I'm back again - now I'm trying to connect to a Netware client. Again, the netware box is registered correctly in our DNS. From the Netware README on the download site, I believe I don't need to install anything on the netware server, just run smsstart to load TSAFS etc, which I've done.
On my Linux server, I've tried to add the netware server (mail.domain.com). I've chosen Netware for the Operating System & CTRL for the Access mode. Interfaces has the FQDN of the Netware box. On the NetwareAccess tab, I entered our admin user name: admin.hamilton and it's password. I've also tried just using admin as the username.
I've tried both testserv (my linux server) and mail.hamcoll.sa.edu.au in the Mover setting.
The firewall on the Linux server is OFF.

Here's the contents of the log:
2009-09-10 15:29:01 DEBUG - ClientDialog.switchNetwareMode: platform: NETWARE os: NetWare
2009-09-10 15:32:15 DEBUG - SesamRemoteShell(LocalDBConns [serverName=testserv.domain.com, rmiPort=11401])...
2009-09-10 15:32:15 INFO - sm_gui_request"test.jvr"imoore"S"sm_config_client -c mail.domain.com -o "NetWare" -l 0 -a via_nameserver -m CTRL "
2009-09-10 15:32:15 INFO - SesamRemoteShell.callRemoteShell(0) commandString='sm_gui_request"test.jvr"imoore"S"sm_config_client -c mail.domain.com -o "NetWare" -l 0 -a via_nameserver -m CTRL "'
2009-09-10 15:32:16 INFO - check LD_LIBRARY_PATH=/opt/sesam/bin/sesam/:/opt/sesam/bin/db/::/usr/local/lib:/usr/local/pgsql/lib:/opt/sesam/bin/sms:/opt/novell/lib
check LD_LIBRARY_PATH=/opt/sesam/bin/sesam/:/opt/sesam/bin/db/::/usr/local/lib:/usr/local/pgsql/lib:/opt/sesam/bin/sms:/opt/novell/lib

"test.jvr" "imoore" "E012-HOSTS Backup from mail.domain.com not possible."

2009-09-10 15:32:24 DEBUG - SesamRemoteShell(LocalDBConns [serverName=testserv.domain.com, rmiPort=11401])...
2009-09-10 15:32:24 INFO - sm_gui_request"test.jvr"imoore"S"sm_config_client -c mail.domain.com -o "NetWare" -l 0 -a via_nameserver -m CTRL "
2009-09-10 15:32:24 INFO - SesamRemoteShell.callRemoteShell(0) commandString='sm_gui_request"test.jvr"imoore"S"sm_config_client -c mail.domain.com -o "NetWare" -l 0 -a via_nameserver -m CTRL "'
2009-09-10 15:32:26 INFO - sh: sbc_smdr: command not found

"test.jvr" "imoore" "E002-HOSTS There is no access to computer mail.domain.com - please configure it now for testserv."

ossi1001
Posts: 77
Joined: May 15th, 2009, 10:41 am

Re: Client Server connection problem

Post by ossi1001 » September 10th, 2009, 11:47 am

You have to adjust the datamover for the NetWare server. First you have to install the sesam-novell-client at one of your Linux machines, where the package novell-sms is already installed. You can download the package here:
http://download.sep.de/netware/OES-Linux/

This client will be used as datamover, which sends and receives the data from/to the NetWare server.
Edit the NetWare client in Sesam, switch to the tab NetWare Access and insert the name of the host, where the sesam-novell-client is installed.

I will forward this to SEP, so they can change the documentation.

Regards, Florian

ian
Posts: 15
Joined: September 4th, 2009, 5:36 am
Spam Stop: No
SEP sesam: Software

Re: Client Server connection problem

Post by ian » September 10th, 2009, 12:22 pm

Thanks for that - if I install the novell-sms package on my linux sesam server (testserv), can that act as the datamover as well as being the sesam server itself, or does it have to be a separate server?
In other words can I have a netware server backing up to the linux server, or do I need 3 servers - netware, linux client & linux server?

Thanks again,
Ian

ian
Posts: 15
Joined: September 4th, 2009, 5:36 am
Spam Stop: No
SEP sesam: Software

Re: Client Server connection problem

Post by ian » September 11th, 2009, 1:46 am

Hi, I'm still having trouble with this!

I've just installed the sesam-novell-client-3.4.1-79.SuSE.i586.rpm on the OES linux server I configured originally. This is a SESAM client & already had sesam_cli-3.4.1-67.sles10.i586.rpm installed.
smdrd is running and I can do backups of that server.

I've set that server (hamfp01v.domain.com) as the Data Mover for my Netware server (mail.domain.com). When I check Client Access for the Netware server, I still get:
2009-09-11 08:54:38 DEBUG - ClientDialog.switchNetwareMode: platform: NETWARE os: NetWare
2009-09-11 08:55:01 DEBUG - ClientDialog.switchNetwareMode: platform: NETWARE os: NetWare
2009-09-11 08:55:05 DEBUG - ClientDialog.switchNetwareMode: platform: NETWARE os: NetWare
2009-09-11 08:55:13 DEBUG - SesamRemoteShell(LocalDBConns [serverName=testserv.domain.com, rmiPort=11401])...
2009-09-11 08:55:13 INFO - sm_gui_request"test.jvr"imoore"S"sm_config_client -c mail.domain.com -o "NetWare" -l 0 -a via_nameserver -m CTRL "
2009-09-11 08:55:13 INFO - SesamRemoteShell.callRemoteShell(0) commandString='sm_gui_request"test.jvr"imoore"S"sm_config_client -c domain.com -o "NetWare" -l 0 -a via_nameserver -m CTRL "'
2009-09-11 08:55:14 INFO -
"test.jvr" "imoore" "E002-HOSTS There is no access to computer mail.domain.com - please configure it now for testserv."
Do I need to allow access somehow? Is CTRL the correct Access Mode?
PS: firewall is off on the OES server that is the Data Mover.

Cheers,
Ian

ian
Posts: 15
Joined: September 4th, 2009, 5:36 am
Spam Stop: No
SEP sesam: Software

Re: Client Server connection problem

Post by ian » September 11th, 2009, 6:19 am

A little more info:
If I run:
/opt/sesam/bin/sesam/sbc_smdr -D -N "mail:::admin.hamilton:<password>:0" "/NetWare/MAIL.NetWare File System"
&
/opt/sesam/bin/sesam/sbc_smdr -D -N "mail:::admin.hamilton:<password>:0" "/NetWare/MAIL.Groupwise System"
on the "Data Mover" server (hampf01v which is the OES2SP2 server), it shows all the TSA targets on the MAIL server correctly.

ian
Posts: 15
Joined: September 4th, 2009, 5:36 am
Spam Stop: No
SEP sesam: Software

Re: Client Server connection problem - SOLVED

Post by ian » September 11th, 2009, 6:28 am

I deleted the server in the GUI & recreated it and now it works. :D
The only change I did make was to use mail instead of mail.domain.com as the name of the server, perhaps that was the problem.

DanR
Posts: 5
Joined: October 8th, 2009, 12:44 am
Spam Stop: No
SEP sesam: Software

Re: Client Server connection problem

Post by DanR » October 8th, 2009, 1:12 am

I am having the same problem. One server running sles10sp2 with sesam server. another running sles10sp oes with nss volumes. I can backup and restore to this server, no problem. but the Netware 6.5sp7 server I get the error

2009-10-01 15:42:06 DEBUG - ClientDialog.switchNetwareMode: platform: NETWARE os: NetWare
2009-10-01 15:42:11 DEBUG - SesamRemoteShell(LocalDBConns [serverName=sep2.oregonian.com, rmiPort=11401])...
2009-10-01 15:42:11 INFO - sm_gui_request"test.jvr"root"S"sm_config_client -c NEWSDATS_FS -o "NetWare" -l 2 -a via_nameserver -m CTRL "
2009-10-01 15:42:11 INFO - SesamRemoteShell.callRemoteShell(0) commandString='sm_gui_request"test.jvr"root"S"sm_config_client -c NEWSDATS_FS -o "NetWare" -l 2 -a via_nameserver -m CTRL "'
2009-10-01 15:42:16 INFO - 2009-10-01 15:42:16: scd-3036: Info: # SESAM Control DAEMON (Child Process) FOR UNIX, VERSION: 1.6R14, Released: May 11 2009 #
��� 2009-10-01 15:42:16: scd-1139: Error: CTRLD reply: Could not find executable [sbc_smdr] in defined path(s).

"test.jvr" "root" "E002-HOSTS There is no access to computer NEWSDATS_FS - please configure it now for sep2.

NEWSDATA_FS is the netware server.

I use the sles10sp2 oes as the data mover. It has both novell-sms package and sesam-novell-client installed.
What and where is sbc_smdr? I did a search on the server and it does not exist.

Any help would be great. Thank you - Dan

ossi1001
Posts: 77
Joined: May 15th, 2009, 10:41 am

Re: Client Server connection problem

Post by ossi1001 » October 8th, 2009, 2:43 pm

Hy,

the sbc_smdr is an application, which connects to a NetWare-/OES-server. This file is located at /opt/sesam/bin/sesam, where the package sesam-novell-client is installed.
If I see that correctly, sep2 is your Sesam server and in that case you have to install the sesam-novell-client on this machine, too.

Greetings, Florian

DanR
Posts: 5
Joined: October 8th, 2009, 12:44 am
Spam Stop: No
SEP sesam: Software

Re: Client Server connection problem

Post by DanR » October 8th, 2009, 5:44 pm

Florian,

Thank you! I now can connect and backup and restore NW6.5 and Sles servers :-) I have one more question -- Can you backup data from a SLES server with an NSS volume to a Netware server with an NSS volume. When I try the the restore target only has SLES server listed, not the netware servers.

Thanks again for your help !!!! - Dan

ossi1001
Posts: 77
Joined: May 15th, 2009, 10:41 am

Re: Client Server connection problem

Post by ossi1001 » October 13th, 2009, 2:45 pm

Hy again,

the backup type has to be "NetWare" to restore from an OES to a NetWare server.

Greetings, Florian

DanR
Posts: 5
Joined: October 8th, 2009, 12:44 am
Spam Stop: No
SEP sesam: Software

Re: Client Server connection problem

Post by DanR » October 14th, 2009, 12:03 am

Florian,

Again thanks for your help! Your suggestion made since. So I did a Netware backup of a SLES OES server and it worked fine. When doing a restore, in the target node my only options are other SLES boxes. The Netware server do not show up. Based on your help so I am sure I am doing something simple that is wrong. If you have any other ideas please let me know :-)

Thanks - Dan

ossi1001
Posts: 77
Joined: May 15th, 2009, 10:41 am

Re: Client Server connection problem

Post by ossi1001 » October 16th, 2009, 11:12 am

Hy,

I tested this with Sesam 3.6 and it works. Also I tested with Sesam 3.4 and it didn't work. In that case Sesam 3.4 is the problem. If you want to use this feature, you have to upgrade the Sesam server (and GUI, if you administer it from a remote host).

BR, Florian

Post Reply