Standalone backup agents for Linux, Mac, AIX & Solaris workloads on-premises or in the public cloud
vmlnx2
Novice
Posts: 4Liked: never Joined: Aug 17, 2016 2:47 pm
Contact:
Post
by vmlnx2 Aug 17, 2016 3:20 pm
Hi the endpoint installed succesfully on a Red Hat 7.2 system however the below error message is displayed upon launching the ui:
Code: Select all
sudo veeamservice ui
Server is stopped.
Failed to start Veeam RPC Server
Also please see veeamsvc.1.log below:
Code: Select all
tail -n 20 /var/log/veeam/veeamsvc.1.log
[17.08.2016 10:49:39] <140676348987328> | Ctrl-C thread has been started. ID: [59632]
[17.08.2016 10:49:39] <140676348987328> lpbcore| SQL user version: 2.
[17.08.2016 10:49:39] <140676348987328> lpbcore| Cleaning orphaned sessions.
[17.08.2016 10:49:39] <140676348987328> lpbsvc | Starting server.
[17.08.2016 10:49:39] <140676310570752> | Thread started. Thread id: 140676310570752, parent id: 140676348987328, role: VRPC server thread
[17.08.2016 10:49:39] <140676310570752> net | Veeam RPC server started.
[17.08.2016 10:49:39] <140676310570752> net | ERR |Veeam RPC server broken.
[17.08.2016 10:49:39] <140676310570752> net | >> |Cannot bind socket in CreateEventAndListen() Erno error: [98].
[17.08.2016 10:49:39] <140676310570752> net | >> |An exception was thrown from thread [-1048242432].
[17.08.2016 10:49:39] <140676310570752> | Thread finished. Role: 'VRPC server thread'.
[17.08.2016 10:49:39] <140676348987328> lpbsvc | Disposing clients manager.
[17.08.2016 10:49:39] <140676348987328> lpbsvc | Starting server. Failed.
[17.08.2016 10:49:39] <140676348987328> lpbsvc | Server is stopped.
[17.08.2016 10:49:39] <140676348987328> lpbsvc | ERR |Main thread has failed.
[17.08.2016 10:49:39] <140676348987328> lpbsvc | >> |Failed to start Veeam RPC Server
[17.08.2016 10:49:39] <140676348987328> lpbsvc | >> |An exception was thrown from thread [-1009825856].
[17.08.2016 10:49:39] <140676348987328> | Generating stop signal (CtrlC thread).
[17.08.2016 10:49:39] <140676318963456> | CtrlC thread received stop signal. Exiting.
[17.08.2016 10:49:39] <140676318963456> | Thread finished. Role: 'Ctrl-C thread'.
[17.08.2016 10:49:39] <140676348987328> | Ctrl-C thread stopped.
Thanks!
nielsengelen
Product Manager
Posts: 5797Liked: 1215 times Joined: Jul 15, 2013 11:09 amFull Name: Niels Engelen
Contact:
Post
by nielsengelen Aug 18, 2016 7:09 am
Can you run netstat -pan | grep 3500 and ser if something is running on that port?
Personal blog: https://foonet.be https://github.com/nielsengelen
vmlnx2
Novice
Posts: 4Liked: never Joined: Aug 17, 2016 2:47 pm
Contact:
Post
by vmlnx2 Aug 18, 2016 12:50 pm
Please see output below:
Code: Select all
sudo netstat -pan | grep 3500
tcp 21 0 0.0.0.0:3500 0.0.0.0:* LISTEN 1147/veeamjobman
tcp 36 0 127.0.0.1:3500 127.0.0.1:58881 ESTABLISHED -
tcp 36 0 127.0.0.1:3500 127.0.0.1:34834 ESTABLISHED -
tcp 0 0 127.0.0.1:3500 127.0.0.1:58468 ESTABLISHED 1688/veeamagent
tcp 0 0 127.0.0.1:59625 127.0.0.1:3500 ESTABLISHED 7878/veeamconfig
tcp 0 0 127.0.0.1:60993 127.0.0.1:3500 ESTABLISHED 72674/veeamconfig
tcp 0 0 127.0.0.1:58881 127.0.0.1:3500 ESTABLISHED 47435/veeamconfig
tcp 36 0 127.0.0.1:3500 127.0.0.1:33305 ESTABLISHED -
tcp 36 0 127.0.0.1:3500 127.0.0.1:59008 ESTABLISHED -
tcp 0 0 127.0.0.1:35251 127.0.0.1:3500 ESTABLISHED 15597/veeamconfig
tcp 0 0 127.0.0.1:3500 127.0.0.1:58466 ESTABLISHED 1688/veeamagent
tcp 0 0 127.0.0.1:33305 127.0.0.1:3500 ESTABLISHED 58769/veeamconfig
tcp 36 0 127.0.0.1:3500 127.0.0.1:59269 ESTABLISHED -
tcp 0 0 127.0.0.1:59661 127.0.0.1:3500 ESTABLISHED 37171/veeamconfig
tcp 0 0 127.0.0.1:59008 127.0.0.1:3500 ESTABLISHED 13005/veeamconfig
tcp 0 0 127.0.0.1:59590 127.0.0.1:3500 ESTABLISHED 50937/veeamconfig
tcp 0 0 127.0.0.1:59269 127.0.0.1:3500 ESTABLISHED 16554/veeamconfig
tcp 0 0 127.0.0.1:58466 127.0.0.1:3500 ESTABLISHED 1147/veeamjobman
tcp 0 0 127.0.0.1:3500 127.0.0.1:58469 ESTABLISHED 1688/veeamagent
tcp 36 0 127.0.0.1:3500 127.0.0.1:59522 ESTABLISHED -
tcp 36 0 127.0.0.1:3500 127.0.0.1:60993 ESTABLISHED -
tcp 36 0 127.0.0.1:3500 127.0.0.1:59711 ESTABLISHED -
tcp 0 0 127.0.0.1:59137 127.0.0.1:3500 ESTABLISHED 51103/veeamconfig
tcp 36 0 127.0.0.1:3500 127.0.0.1:59661 ESTABLISHED -
tcp 0 0 127.0.0.1:3500 127.0.0.1:58465 ESTABLISHED 1688/veeamagent
tcp 36 0 127.0.0.1:3500 127.0.0.1:35933 ESTABLISHED -
tcp 36 0 127.0.0.1:3500 127.0.0.1:35251 ESTABLISHED -
tcp 0 0 127.0.0.1:58468 127.0.0.1:3500 ESTABLISHED 1147/veeamjobman
tcp 0 0 127.0.0.1:34834 127.0.0.1:3500 ESTABLISHED 2065/veeamconfig
tcp 36 0 127.0.0.1:3500 127.0.0.1:35669 ESTABLISHED -
tcp 0 0 127.0.0.1:59711 127.0.0.1:3500 ESTABLISHED 67200/veeamconfig
tcp 36 0 127.0.0.1:3500 127.0.0.1:35043 ESTABLISHED -
tcp 0 0 127.0.0.1:35933 127.0.0.1:3500 ESTABLISHED 1068/veeamconfig
tcp 0 0 127.0.0.1:35043 127.0.0.1:3500 ESTABLISHED 45600/veeamconfig
tcp 36 0 127.0.0.1:3500 127.0.0.1:59590 ESTABLISHED -
tcp 0 0 127.0.0.1:59522 127.0.0.1:3500 ESTABLISHED 54165/veeamconfig
tcp 0 0 127.0.0.1:58467 127.0.0.1:3500 ESTABLISHED 1147/veeamjobman
tcp 37 0 127.0.0.1:3500 127.0.0.1:58875 CLOSE_WAIT -
tcp 0 0 127.0.0.1:58469 127.0.0.1:3500 ESTABLISHED 1147/veeamjobman
tcp 37 0 127.0.0.1:3500 127.0.0.1:58858 CLOSE_WAIT -
tcp 0 0 127.0.0.1:58465 127.0.0.1:3500 ESTABLISHED 1147/veeamjobman
tcp 37 0 127.0.0.1:3500 127.0.0.1:58874 CLOSE_WAIT -
tcp 0 0 127.0.0.1:35459 127.0.0.1:3500 ESTABLISHED 57961/veeamconfig
tcp 36 0 127.0.0.1:3500 127.0.0.1:59137 ESTABLISHED -
tcp 36 0 127.0.0.1:3500 127.0.0.1:35459 ESTABLISHED -
tcp 0 0 127.0.0.1:3500 127.0.0.1:58467 ESTABLISHED 1688/veeamagent
tcp 37 0 127.0.0.1:3500 127.0.0.1:58857 CLOSE_WAIT -
tcp 36 0 127.0.0.1:3500 127.0.0.1:59625 ESTABLISHED -
tcp 0 0 127.0.0.1:35669 127.0.0.1:3500 ESTABLISHED 27660/veeamconfig
PTide
Product Manager
Posts: 6551Liked: 765 times Joined: May 19, 2015 1:46 pm
Contact:
Post
by PTide Aug 18, 2016 12:55 pm
Have you tried running just veeam instead of veeamservice ui ?
vmlnx2
Novice
Posts: 4Liked: never Joined: Aug 17, 2016 2:47 pm
Contact:
Post
by vmlnx2 Aug 18, 2016 1:20 pm
It seems the process got stuck after running the command, after waiting for about 5 minutes I had to 'control C' to get the cursor back.
nielsengelen
Product Manager
Posts: 5797Liked: 1215 times Joined: Jul 15, 2013 11:09 amFull Name: Niels Engelen
Contact:
Post
by nielsengelen Aug 18, 2016 2:13 pm
Can you do the following:
Personal blog: https://foonet.be https://github.com/nielsengelen
vmlnx2
Novice
Posts: 4Liked: never Joined: Aug 17, 2016 2:47 pm
Contact:
Post
by vmlnx2 Aug 18, 2016 2:28 pm
I ended up restarting the server after which the command 'veeam' worked, the service appears to be running fine however the command 'veeamservice ui' still gives errors... see output below:
Is there a need to use the 'veeamservice ui' command... or are the 'veeam' and 'veeamconfig' enough to manage all agent oprations?
Code: Select all
sudo systemctl status veeamservice
● veeamservice.service - SYSV: veeam agent service
Loaded: loaded (/etc/rc.d/init.d/veeamservice)
Active: active (running) since Thu 2016-08-18 10:05:36 EDT; 13min ago
Docs: man:systemd-sysv-generator(8)
Process: 5256 ExecStart=/etc/rc.d/init.d/veeamservice start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/veeamservice.service
└─5260 /usr/sbin/veeamservice --daemonize --pidfile=/var/run/veeamservice.pid
Aug 18 10:05:36 D1pSyDB.vitas.com systemd[1]: Starting SYSV: veeam agent service...
Aug 18 10:05:36 D1pSyDB.vitas.com veeamservice[5256]: Starting veeamservice: [ OK ]
Aug 18 10:05:36 D1pSyDB.vitas.com systemd[1]: Started SYSV: veeam agent service.
Aug 18 10:05:36 D1pSyDB.vitas.com veeamservice[5260]: Service started.
Aug 18 10:05:36 D1pSyDB.vitas.com veeamservice[5260]: Initializing log file [/var/log/veeam/veeamsvc.log].
Aug 18 10:16:40 D1pSyDB.vitas.com crontab[5866]: (root) BEGIN EDIT (root)
Aug 18 10:16:40 D1pSyDB.vitas.com crontab[5866]: (root) END EDIT (root)
Aug 18 10:16:40 D1pSyDB.vitas.com crontab[5869]: (root) REPLACE (root)
sudo veeamservice ui
Server is stopped.
Failed to start Veeam RPC Server
Thank you!
nielsengelen
Product Manager
Posts: 5797Liked: 1215 times Joined: Jul 15, 2013 11:09 amFull Name: Niels Engelen
Contact:
Post
by nielsengelen Aug 18, 2016 2:30 pm
veeamservice ui is not a valid command and there is no need for it
.
You can use 2 commands to get to the UI:
veeam
veeamconfig ui
Maybe you mixed up veeamconfig and veeamservice (the last one is pure used for service management).
Good that it works now. Happy testing and looking forward to feedback!
Personal blog: https://foonet.be https://github.com/nielsengelen
Users browsing this forum: No registered users and 3 guests
.