This post is more than 5 years old
9 Posts
0
1029
September 30th, 2015 03:00
Installation problem: No login after step1
Hi,
can anybody comment on the errors in the log below?
09302015 09:17:58 : ############################### boot operation begin
############################
09302015 09:17:58 : exporting environment variable VIPR_DEPLOYMENT_TYPE to fabric
Re-Starting syslog services..done
Launching container fiendly cron.
Launching container fiendly cron.
Launching container fiendly cron.
rm: cannot remove `/opt/storageos/logs': Device or resource busy
09302015 09:17:59 : Parsing /host/data/network.json
09302015 09:17:59 : VERSION: 2.0.1.0.62273.ca0b6cd private iface: eno16777728 public iface:
eno16777728 START VIPR:
09302015 09:17:59 : StorageServer JSON configuration file is /data/partitions.json
09302015 09:17:59 : expecting data partitions to be mounted under /disks
09302015 09:17:59 : setting partitionroot=/disks in /opt/storageos/conf/storageserver.conf
09302015 09:17:59 : partitions.json already exists - will not generate it
09302015 09:17:59 : validating config.iso and fabric version file
09302015 09:17:59 : config.iso is missing in the /data location
09302015 09:17:59 : fetching network information
09302015 09:17:59 : IP address of the machine: 172.25.1.150
09302015 09:17:59 : NETMASK found: 255.255.255.0
09302015 09:17:59 : Created /opt/storageos/conf/network
09302015 09:17:59 : IPADDR='172.25.1.150'
09302015 09:17:59 : All validations are complete. Going ahead with the configuration steps.
09302015 09:17:59 : populating vipr shared library path
09302015 09:17:59 : /opt/storageos/lib is already populated
09302015 09:17:59 : creating scsi device nodes
09302015 09:18:06 : creating volumes skeleton containers
09302015 09:18:06 : populating vipr network info in fabric identifier
09302015 09:18:06 : fixing svcuser account permissions
09302015 09:18:06 : updating storageos property to datanode
09302015 09:18:06 : fixing file permissions
09302015 09:18:06 : fixing storageos and data ownership
09302015 09:18:07 : creating place holders file
09302015 09:18:07 : preparing vipr configuration information
cp: cannot stat `/data/config.iso': No such file or directory
09302015 09:18:07 : registering supporting services
boot.ovfenv 0:off 1:off 2:off 3:off 4:off 5:off 6:off B:on
connectemc 0:off 1:off 2:off 3:on 4:off 5:on 6:off
nginx 0:off 1:off 2:off 3:on 4:off 5:on 6:off
insserv: FATAL: service boot.clock has to be enabled to use service storageos-dataservice
insserv: exiting now!
/sbin/insserv failed, exit code 1
storageos-dataservice 0:off 1:off 2:off 3:off 4:off 5:off 6:off
09302015 09:18:07 : starting boot.ovfenv service
Initializing configuration properties
..done
Generating configuration files
/etc/systool: Warning: Fabric deployment. Skipping _bootfs_mount_ro()
..failed
/etc/init.d/storageos-dataservice: line 99: /proc/sys/kernel/core_pattern: Read-only file system
Warning: Found stale pidfile(s) (unclean shutdown?)
Setting up SSL certificates..done
Starting ViPR servicesgrep: /proc/scsi/sg/device_strs: No such file or directory
..done
Shutting down CRON daemon..done
Starting CRON daemon..done
Starting nginx service
..done
Starting ConnectEMC service..done


JasonCwik
281 Posts
0
March 18th, 2016 07:00
Sorry for the late reply on this topic. Those error messages are benign and don't impact the container startup. There were some other issues at this time that were impacting boot and should be fixed in the latest builds.