topic Re: Migration Deployment server error in Deployment Architecture https://community.splunk.com/t5/Deployment-Architecture/Migration-Deployment-server-error/m-p/444000#M15638 <P>On the clients (forwarders), did you update the deploymentclient.conf to point to your new deployment server and restart it?</P> Wed, 01 May 2019 09:01:57 GMT lakshman239 2019-05-01T09:01:57Z Migration Deployment server error https://community.splunk.com/t5/Deployment-Architecture/Migration-Deployment-server-error/m-p/443998#M15636 <P>I did a migration from old splunk to new splunk. after configuring serverclasses i found some devices sending logs but all of sudden i am not seeing any devices phoned in. Here is the logs for one Device. the last log says the action:Uninstall. what does that mean ? Now when i try to restart splunk from client machine is giving me "ERROR: pid 2968 terminated with signal 11 (core dumped)<BR /> SSL certificate generation failed." Error. </P> <P>04-30-2019 09:32:18.609 -0700 INFO ClientSessionsManager:Listener_AppEvents - Received count=3 AppEvents from DC ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44<BR /> 04-30-2019 09:42:19.562 -0700 INFO ClientSessionsManager:Listener_AppEvents - Received count=3 AppEvents from DC ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44<BR /> 04-30-2019 09:52:20.515 -0700 INFO ClientSessionsManager:Listener_AppEvents - Received count=3 AppEvents from DC ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44<BR /> 04-30-2019 10:02:21.493 -0700 INFO ClientSessionsManager:Listener_AppEvents - Received count=3 AppEvents from DC ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44<BR /> 04-30-2019 10:11:25.399 -0700 INFO PubSubSvr - Subscribed: channel=deploymentServer/phoneHome/default/reply/sjebsdb04.netgear.com/4A4C403F-B870-4D58-8259-189DB74E4D44 connectionId=connection_10.100.0.135_8089_sjebsdb04.netgear.com_sjebsdb04.netgear.com_4A4C403F-B870-4D58-8259-189DB74E4D44 listener=0x7fd2d46dda00<BR /> 04-30-2019 10:11:25.423 -0700 INFO PubSubSvr - Subscribed: channel=tenantService/handshake/reply/sjebsdb04.netgear.com/4A4C403F-B870-4D58-8259-189DB74E4D44 connectionId=connection_10.100.0.135_8089_sjebsdb04.netgear.com_sjebsdb04.netgear.com_4A4C403F-B870-4D58-8259-189DB74E4D44 listener=0x7fd2d46dda00<BR /> 04-30-2019 10:12:25.265 -0700 INFO ClientSessionsManager - Adding client: ip=10.100.0.135 uts=linux-x86_64 id=4A4C403F-B870-4D58-8259-189DB74E4D44 name=4A4C403F-B870-4D58-8259-189DB74E4D44<BR /> 04-30-2019 10:12:25.265 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_nix app=Splunk_TA_nix: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:12:25.266 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_deploymentclient app=netgear_all_deploymentclient: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:12:25.266 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_deploymentclient app=netgear_all_forwarder_outputs: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:12:25.266 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_forwarder_outputs app=netgear_all_forwarder_outputs: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:12:25.266 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_forwarders app=netgear_all_forwarder_outputs: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:12:25.289 -0700 INFO ClientSessionsManager:Listener_AppEvents - Received count=3 AppEvents from DC ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44<BR /> 04-30-2019 10:12:25.289 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 Updating record for sc=netgear_all_deploymentclient app=netgear_all_deploymentclient: action=Install result=Ok checksum=13412163369467275487<BR /> 04-30-2019 10:12:25.289 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 Updating record for sc=netgear_all_deploymentclient app=netgear_all_forwarder_outputs: action=Install result=Ok checksum=15491986698083571770<BR /> 04-30-2019 10:12:25.289 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 Updating record for sc=netgear_all_nix app=Splunk_TA_nix: action=Install result=Ok checksum=13350837051104395546<BR /> 04-30-2019 10:15:25.616 -0700 INFO PubSubSvr - Subscribed: channel=deploymentServer/phoneHome/default/reply/sjebsdb04.netgear.com/4A4C403F-B870-4D58-8259-189DB74E4D44 connectionId=connection_10.100.0.135_8089_sjebsdb04.netgear.com_sjebsdb04.netgear.com_4A4C403F-B870-4D58-8259-189DB74E4D44 listener=0x7fa537a57a00<BR /> 04-30-2019 10:15:25.639 -0700 INFO PubSubSvr - Subscribed: channel=tenantService/handshake/reply/sjebsdb04.netgear.com/4A4C403F-B870-4D58-8259-189DB74E4D44 connectionId=connection_10.100.0.135_8089_sjebsdb04.netgear.com_sjebsdb04.netgear.com_4A4C403F-B870-4D58-8259-189DB74E4D44 listener=0x7fa537a57a00<BR /> 04-30-2019 10:16:25.482 -0700 INFO ClientSessionsManager - Adding client: ip=10.100.0.135 uts=linux-x86_64 id=4A4C403F-B870-4D58-8259-189DB74E4D44 name=4A4C403F-B870-4D58-8259-189DB74E4D44<BR /> 04-30-2019 10:16:25.483 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_nix app=Splunk_TA_nix: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:16:25.483 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_deploymentclient app=netgear_all_deploymentclient: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:16:25.483 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_deploymentclient app=netgear_all_forwarder_outputs: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:16:25.483 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_forwarder_outputs app=netgear_all_forwarder_outputs: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:16:25.483 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_forwarders app=netgear_all_forwarder_outputs: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:21:26.000 -0700 WARN PubSubSvr - sender=connection_10.100.0.135_8089_sjebsdb04.netgear.com_sjebsdb04.netgear.com_4A4C403F-B870-4D58-8259-189DB74E4D44 channel=deploymentServer/phoneHome/default Message not dispatched (connection invalid)<BR /> 04-30-2019 10:22:26.230 -0700 INFO PubSubSvr - Subscribed: channel=deploymentServer/phoneHome/default/reply/sjebsdb04.netgear.com/4A4C403F-B870-4D58-8259-189DB74E4D44 connectionId=connection_10.100.0.135_8089_sjebsdb04.netgear.com_sjebsdb04.netgear.com_4A4C403F-B870-4D58-8259-189DB74E4D44 listener=0x7faf1f6b9400<BR /> 04-30-2019 10:22:26.253 -0700 INFO PubSubSvr - Subscribed: channel=tenantService/handshake/reply/sjebsdb04.netgear.com/4A4C403F-B870-4D58-8259-189DB74E4D44 connectionId=connection_10.100.0.135_8089_sjebsdb04.netgear.com_sjebsdb04.netgear.com_4A4C403F-B870-4D58-8259-189DB74E4D44 listener=0x7faf1f6b9400<BR /> 04-30-2019 10:23:26.096 -0700 INFO ClientSessionsManager - Adding client: ip=10.100.0.135 uts=linux-x86_64 id=4A4C403F-B870-4D58-8259-189DB74E4D44 name=4A4C403F-B870-4D58-8259-189DB74E4D44<BR /> 04-30-2019 10:23:26.096 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_nix app=Splunk_TA_nix: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:23:26.096 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_deploymentclient app=netgear_all_deploymentclient: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:23:26.096 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_forwarder_outputs app=netgear_all_forwarder_outputs: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:23:26.096 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_forwarders app=netgear_all_forwarder_outputs: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:23:26.096 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_deploymentclient app=netgear_all_forwarder_outputs: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:23:26.120 -0700 INFO ClientSessionsManager:Listener_AppEvents - Received count=3 AppEvents from DC ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44<BR /> 04-30-2019 10:23:26.120 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 Updating record for sc=netgear_all_deploymentclient app=netgear_all_deploymentclient: action=Install result=Ok checksum=13412163369467275487<BR /> 04-30-2019 10:23:26.120 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 Updating record for sc=netgear_all_deploymentclient app=netgear_all_forwarder_outputs: action=Install result=Ok checksum=15491986698083571770<BR /> 04-30-2019 10:23:26.120 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 Updating record for sc=netgear_all_nix app=Splunk_TA_nix: action=Install result=Ok checksum=13350837051104395546<BR /> 04-30-2019 10:29:26.698 -0700 WARN PubSubSvr - sender=connection_10.100.0.135_8089_sjebsdb04.netgear.com_sjebsdb04.netgear.com_4A4C403F-B870-4D58-8259-189DB74E4D44 channel=deploymentServer/phoneHome/default Message not dispatched (connection invalid)<BR /> 04-30-2019 10:30:26.933 -0700 INFO PubSubSvr - Subscribed: channel=deploymentServer/phoneHome/default/reply/sjebsdb04.netgear.com/4A4C403F-B870-4D58-8259-189DB74E4D44 connectionId=connection_10.100.0.135_8089_sjebsdb04.netgear.com_sjebsdb04.netgear.com_4A4C403F-B870-4D58-8259-189DB74E4D44 listener=0x7f6454d4c400<BR /> 04-30-2019 10:30:26.956 -0700 INFO PubSubSvr - Subscribed: channel=tenantService/handshake/reply/sjebsdb04.netgear.com/4A4C403F-B870-4D58-8259-189DB74E4D44 connectionId=connection_10.100.0.135_8089_sjebsdb04.netgear.com_sjebsdb04.netgear.com_4A4C403F-B870-4D58-8259-189DB74E4D44 listener=0x7f6454d4c400<BR /> 04-30-2019 10:31:26.801 -0700 INFO ClientSessionsManager - Adding client: ip=10.100.0.135 uts=linux-x86_64 id=4A4C403F-B870-4D58-8259-189DB74E4D44 name=4A4C403F-B870-4D58-8259-189DB74E4D44<BR /> 04-30-2019 10:31:26.801 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_nix app=Splunk_TA_nix: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:31:26.801 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_deploymentclient app=netgear_all_deploymentclient: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:31:26.801 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_deploymentclient app=netgear_all_forwarder_outputs: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:31:26.801 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_forwarder_outputs app=netgear_all_forwarder_outputs: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:31:26.801 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_forwarders app=netgear_all_forwarder_outputs: action=Phonehome result=Ok checksum=0<BR /> 04-30-2019 10:40:23.257 -0700 INFO PubSubSvr - Subscribed: channel=deploymentServer/phoneHome/default/reply/sjebsdb04.netgear.com/4A4C403F-B870-4D58-8259-189DB74E4D44 connectionId=connection_10.100.0.135_8089_sjebsdb04.netgear.com_sjebsdb04.netgear.com_4A4C403F-B870-4D58-8259-189DB74E4D44 listener=0x7f0394ff0000<BR /> 04-30-2019 10:40:23.281 -0700 INFO PubSubSvr - Subscribed: channel=tenantService/handshake/reply/sjebsdb04.netgear.com/4A4C403F-B870-4D58-8259-189DB74E4D44 connectionId=connection_10.100.0.135_8089_sjebsdb04.netgear.com_sjebsdb04.netgear.com_4A4C403F-B870-4D58-8259-189DB74E4D44 listener=0x7f0394ff0000<BR /> 04-30-2019 10:40:26.873 -0700 INFO ClientSessionsManager - Adding client: ip=10.100.0.135 uts=linux-x86_64 id=4A4C403F-B870-4D58-8259-189DB74E4D44 name=4A4C403F-B870-4D58-8259-189DB74E4D44<BR /> 04-30-2019 10:40:26.961 -0700 INFO ClientSessionsManager:Listener_AppEvents - Received count=3 AppEvents from DC ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44<BR /> 04-30-2019 10:40:26.961 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_deploymentclient app=netgear_all_deploymentclient: action=Uninstall result=Ok checksum=0<BR /> 04-30-2019 10:40:26.961 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_deploymentclient app=netgear_all_forwarder_outputs: action=Uninstall result=Ok checksum=0<BR /> 04-30-2019 10:40:26.961 -0700 INFO ClientSessionsManager - ip=10.100.0.135 name=4A4C403F-B870-4D58-8259-189DB74E4D44 New record for sc=netgear_all_nix app=Splunk_TA_nix: action=Uninstall result=Ok checksum=0</P> Wed, 30 Sep 2020 00:23:56 GMT https://community.splunk.com/t5/Deployment-Architecture/Migration-Deployment-server-error/m-p/443998#M15636 jprakash_netgea 2020-09-30T00:23:56Z Re: Migration Deployment server error https://community.splunk.com/t5/Deployment-Architecture/Migration-Deployment-server-error/m-p/443999#M15637 <P>I tired restarting other server, the splunk service started on that machine. But no device phoned to new / old deployment server</P> Tue, 30 Apr 2019 23:13:07 GMT https://community.splunk.com/t5/Deployment-Architecture/Migration-Deployment-server-error/m-p/443999#M15637 jprakash_netgea 2019-04-30T23:13:07Z Re: Migration Deployment server error https://community.splunk.com/t5/Deployment-Architecture/Migration-Deployment-server-error/m-p/444000#M15638 <P>On the clients (forwarders), did you update the deploymentclient.conf to point to your new deployment server and restart it?</P> Wed, 01 May 2019 09:01:57 GMT https://community.splunk.com/t5/Deployment-Architecture/Migration-Deployment-server-error/m-p/444000#M15638 lakshman239 2019-05-01T09:01:57Z Re: Migration Deployment server error https://community.splunk.com/t5/Deployment-Architecture/Migration-Deployment-server-error/m-p/444001#M15639 <P>Check the user:group permissions on your deploymentclient.conf file.</P> <P>Also, if you defined your targetUri by hostname (not ip addr) then make certain that hostname resolves in DNS (or in /etc/hosts).</P> <PRE><CODE>nslookup your.host.name.com </CODE></PRE> Wed, 01 May 2019 15:16:40 GMT https://community.splunk.com/t5/Deployment-Architecture/Migration-Deployment-server-error/m-p/444001#M15639 codebuilder 2019-05-01T15:16:40Z