v3.5 Troubleshooting

#	Specific Condition	Symptom	Suggested Resolution
1	High concurrency level configured	"Too many open files" error messages	Increase open files count limit, for example using the following shell command: ulimit -n 1048576
2	HTTP Storage Driver	403 responses from the storage with message "time too skewed"	Align the clients system clock time with storage system clock
3	Mongoose storage driver host has multiple external network interfaces configured and Java RMI server implementation bounds Mongoose service to a wrong (private) interface	Mongoose controller fails to connect the Mongoose storage driver because it binds to an IP that cannot be accessed from other hosts	You can explicitly specify the network interface to use via native Java's java.rmi.server.hostname configuration parameter. For example: $ java -Djava.rmi.server.hostname=123.45.67.89 -jar mongoose-storage-driver-service.jar
4	Load using large data items I/O	Observed bandwidth is lower than using v3.4.x	Use lower load-service-threads value (1 or 2)
5	- Default ("s3") storage driver used - "x-emc-*" custom header(s) is configured	403 responses from the storage with message "signature mismatch"	Use "emcs3" storage driver