We are running Ubuntu 14.04 LTS with 2GB RAM and 2 cores on a 64-bit VM from VMWare.
The setup logs seem to have an error regarding the Asimba setup, q.v. the relevant portions of the stack traces below.
03:17:19 11/30/15 Error copying ./output/asimba.xml to /opt/dist/tmp_asimba/WEB-INF/conf/asimba.xml
03:17:19 11/30/15 Traceback (most recent call last):
File "./setup.py", line 460, in copyFile
shutil.copy(inFile, destFolder)
File "/usr/lib/python2.7/shutil.py", line 119, in copy
copyfile(src, dst)
File "/usr/lib/python2.7/shutil.py", line 83, in copyfile
with open(dst, 'wb') as fdst:
IOError: [Errno 2] No such file or directory: '/opt/dist/tmp_asimba/WEB-INF/conf/asimba.xml'
03:17:19 11/30/15 Running: /usr/bin/jar cmf tmp_asimba/META-INF/MANIFEST.MF asimba.war -C /opt/dist/tmp_asimba/ .
03:17:19 11/30/15 java.io.FileNotFoundException: tmp_asimba/META-INF/MANIFEST.MF (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:146)
at java.io.FileInputStream.<init>(FileInputStream.java:101)
at sun.tools.jar.Main.run(Main.java:172)
at sun.tools.jar.Main.main(Main.java:1231)
03:17:19 11/30/15 Copying asimba.war into tomcat webapps folder...
03:17:19 11/30/15 Error copying /opt/dist/asimba.war to /opt/tomcat/webapps
03:17:19 11/30/15 Traceback (most recent call last):
File "./setup.py", line 460, in copyFile
shutil.copy(inFile, destFolder)
File "/usr/lib/python2.7/shutil.py", line 119, in copy
copyfile(src, dst)
File "/usr/lib/python2.7/shutil.py", line 82, in copyfile
with open(src, 'rb') as fsrc:
IOError: [Errno 2] No such file or directory: '/opt/dist/asimba.war'
**However**
When trying to access https://localhost from Firefox, we are prompted with the following error message:
An error occurred during a connection to localhost. SSL received a record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_long)
I verified that the Apache2 server is listening on port 443 by typing **netstat -pnlt | grep '443'**
What could be wrong with the server configuration that would result in the admin console giving this error and not being visible. We feel that the Asimba error, while certainly being a problem, is not the cause of the admin console not loading.