Cannot Start Crs Service System Error 1053 Unknown Error 1053
Contents |
error code 1053 on Linux doesn't have any particular meaning. It's just a catch-all to say "something went wrong during service startup". I've experienced this twice now, and both times
Cannot Start "hpdp-idb" Service, System Error:
it was for different reasons. Here's the output from omnisv status... hpdp-idb-cp down ProcName Status [PID] =============================== crs
Hpdp Services
: Active [26506] mmd : Active [26504] kms : Active [26505] hpdp-idb : Active [26466] hpdp-idb-cp : Active [26499] hpdp-as : Down omnitrig : Active Sending of traps disabled. =============================== With a bit of inspired guessing, hpdp-as is supposed to be started by /etc/rc.d/init.d/hpdp-as. Despite what it looks like, this isn't actually used as SYSV init runscript -- it is invoked by /opt/omni/sbin/omnisv start. This in turn is invoked by /etc/rc.d/init.d/omni, which actually is a SYSV init runscript. /etc/rc.d/init.d/hpdp-as isn't part of any RPM file; neither are any of the other Data Protector start up scripts. /etc/init.d/omni is installed by the OB2-CS post-install scriptlet. /etc/init.d/hpdp-as is created by the IDBsetup.sh script when it calls an internally-defined updateServices function The first time I encounted "Unknown error 1053", it was simply because something had gone wrong during installation, and /etc/init.d/hpdp-as wasn't created. I just took the code from IDBsetup.sh (search for hpdp-as and you'll find an init script inside a heredoc) and recreated it. Then I checked that the appropriate /etc/services entry had been created ( "hpdp-idb-as 7116/tcp" ) If this happens to you, here's a handy /etc/init.d/hpdp-as for reference. Just change lnx.ifost.org.au to whatever your cell manager's hostname is: #!/bin/sh # chkconfig: 35 99 08 # description: HP Data Protector Application Server. # processname: hpdp-as ### BEGIN INIT INFO # Provides: hpdp-as # Required-Start: $local_fs $remote_fs $network $syslog # Required-Stop: $local_fs $remote_fs $netwo
Things Small and Medium Business Service Providers All Solutions Services Advise, Transform and Manage Financing and Flexible Capacity IT Support Services Education and Training Services All Services Products Integrated Systems Composable Systems Converged Systems Hyper Converged Systems Blade Systems Infrastructure Management Software Application Lifecycle Management Application Delivery Management Big Data Analytics DevOps Enterprise Security Hybrid and Private Cloud Information Governance Information Management IT Service Management Operations Management Server Management Software as a Service (SaaS) http://blog.ifost.org.au/2014/10/unknown-error-1053-starting-hpdp-as.html Software-Defined Data Center Storage Management All Software Servers Rack Servers Tower Servers Blade Servers Density Optimized Mission Critical Servers Servers for Cloud Server Management All Servers Storage All-flash and Hybrid Storage Midrange and Enterprise Storage Entry Storage Systems Data Availability, Protection and Retention Software Defined Storage Management and Orchestration Storage https://community.hpe.com/t5/Data-Protector-Practitioners/Problem-Start-omnisv-linux/td-p/4726925 Networking All Storage Networking Switches Routers Access Points and Controllers Wireless LAN Campus and Branch Networking Data Center Networking Wide Area Network Software Defined Networking Network Functions Virtualization Network Management All Networking About UsSupportClearType to search2086159Solutions Transform to a Hybrid Infrastructure Protect Your Digital Enterprise Empower the Data-Driven Organization Enable Workplace Productivity Cloud Security Big Data Mobility Infrastructure Internet of Things Small and Medium Business Service Providers All Solutions Services Advise, Transform and Manage Financing and Flexible Capacity IT Support Services Education and Training Services All Services Products Integrated Systems Composable Systems Converged Systems Hyper Converged Systems Blade Systems Infrastructure Management Software Application Lifecycle Management Application Delivery Management Big Data Analytics DevOps Enterprise Security Hybrid and Private Cloud Information Governance Information Management IT Service Management Operations Management Server Management Software as a Service (SaaS) Software-Defined Data Center Storage Management All Software Servers Rack Servers Tower Servers Blade Servers Density Optimize
account properties A specific service has not been found MMD fails upon starting the CRS service Problems starting Data Protector daemons on UNIX Introduction Data Protector Cell Manager daemon http://helpfiles.intactcloud.com/DP/8.00/uiolh/Troubleshooting/Task/HOW_Troubleshooting_OmniBack_II_Services_and_Daemons.htm could not be started The hpdp-idb service fails to start, reporting shared memory http://helpfiles.intactcloud.com/dp/8.00/uiolh/troubleshooting/task/how_troubleshooting_omniback_ii_installation.htm deficiency MMD fails upon starting the CRS service Other problems with Data Protector processes Data Protector performance on Red Hat Enterprise Linux is lower than on other operating systems Introduction The Data Protector services (Windows systems) and daemons (UNIX systems) run on the Cell Manager. Run the omnisv -status cannot start command to check whether services/daemons are running. If the Data Protector services/daemons seem to be stopped or have not been installed on the target Data Protector client, make sure that you do not have a name resolution problem. Related task A list of Data Protector processes The following table shows which processes run while Data Protector is idle or performing some basic operations, cannot start crs such as a backup, a restore, or a media management session. Always Backup Restore Media management Cell Manager Windows omniinet.exe mmd.exe crs.exe kms.exe hpdp-idb hpdp-idb-cp hpdp-as bsm.exe rsm.exe msm.exe UNIX mmd crs kms hpdp-idb (postgres) hpdp-idb-cp (pgbouncer) hpdp-as (standalone.sh) bsm rsm msm Disk Agent client Windows omniinet.exe vbda.exe vrda.exe UNIX vbda vrda Media Agent client Windows omniinet.exe bma.exe rma.exe mma.exe UNIX bma rma mma You do not have permission to start the services Problem The following error displays: Could not start the ServiceName on SystemName. Access is denied. Action The system administrator should grant you the permission to start, stop, and modify services on the system that you administer. Changed service account properties Problem If the service account does not have the permission to start the service or if the service account properties (for example, the password) have been changed, the following error displays: The Data Protector Inet service failed to start due to the following error: The service did not start due to a logon failure. Action In the Windows Control Panel > Administrative Tools > Services, modify
on Windows systems Problems with remote installation of Windows clients Problems with remote installation of UNIX clients Check the system's log files on UNIX and setup log files on Windows to determine the problem: System Log file UNIX (local installation) /var/adm/sw/swinstall.log /var/adm/sw/swagent.log UNIX (remote installation) /var/opt/omni/log/IS_install.log Windows (local installation) System_disk:\Temp\OB2_Setup_ui_Date_Time.txt Windows (remote installation) System_disk:\Temp\OB2_Setup_exe_Date_Time.txt If the setup log files were not created, run the installation with the debug option. Name resolution problems when installing the Windows Cell Manager During the installation of the Windows Cell Manager, Data Protector detects and warns you if the DNS or the LMHOSTS file is not set up as required. In addition, Data Protector notifies you if the TCP/IP protocol is not installed on your system. Problem If the name resolution fails, the “error expanding hostname” message is displayed and the installation is aborted. If you encounter resolution problems when using DNS, you get a warning message about your current DNS configuration. If you encounter resolution problems when using LMHOSTS file, you get a warning message to check your LMHOSTS file configuration. If you have not configured either DNS or LMHOSTS, you get a warning message to enable the DNS or the LMHOSTS resolution in the TCP/IP properties dialog. Action Check your DNS or LMHOSTS file configuration or activate it. Related tasks Problem If the TCP/IP protocol is not installed and configured on your system, the installation is aborted. Data Protector uses the TCP/IP protocol for network communications; it must be installed and configured on every client system in the cell. Action Check the TCP/IP setup. Related tasks Problems with installation