Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improved logging for selenium docker-compose problems. #3264

Merged
merged 3 commits into from Dec 8, 2016

Conversation

Projects
None yet
2 participants
@jmchilton
Copy link
Member

commented Dec 5, 2016

If containers fail to start, (as the Galaxy container for the selenium test appears to fail currently) print docker logs for that container.

Improved logging for selenium docker-compose problems.
If containers fail to start, (as the Galaxy container for the selenium test appears to fail currently) print docker logs for that container.

@jmchilton jmchilton added this to the 17.01 milestone Dec 5, 2016

@jmchilton

This comment has been minimized.

Copy link
Member Author

commented Dec 5, 2016

The Galaxy container cannot see postgres during startup anymore. Maybe network problems - too many Docker network created during testing that need to be cleaned up?

Creating network "selenium13_default" with the default driver
Creating selenium13_postgres_1
Creating selenium13_galaxy_1
Creating selenium13_selenium_1
Waiting on service postgres
Service postgres ready - with container ID 79a2429fe620
Waiting on service galaxy
Service galaxy ready - with container ID 7b501c66125b
Waiting on service selenium
Service selenium ready - with container ID 38d1be10cdb0
Waiting on docker-compose managed Galaxy server - http://localhost:37354/.
......Service galaxy stopped before Galaxy came up, exiting and halting containers.
Dumping logs for postgres container (79a2429fe620)...
---
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

Success. You can now start the database server using:

    pg_ctl -D /var/lib/postgresql/data -l logfile start


WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
****************************************************
WARNING: No password has been set for the database.
         This will allow anyone with access to the
         Postgres port to access your database. In
         Docker's default configuration, this is
         effectively any other container on the same
         system.

         Use "-e POSTGRES_PASSWORD=password" to set
         it in "docker run".
****************************************************
---
Dumping logs for galaxy container (7b501c66125b)...
---
Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda2 236382208 147604240 77136976 66% / tmpfs 16541320 0 16541320 0% /dev tmpfs 16541320 0 16541320 0% /sys/fs/cgroup /dev/sda2 236382208 147604240 77136976 66% /galaxy shm 65536 0 65536 0% /dev/shm
Creating postgres database for Galaxy
createdb: could not connect to database template1: could not connect to server: Connection refused
	Is the server running on host "postgres" (172.23.0.2) and accepting
	TCP/IP connections on port 5432?
---
Dumping logs for selenium container (38d1be10cdb0)...
---
05:44:40.980 INFO - Selenium build info: version: '3.0.1', revision: '1969d75'
05:44:41.052 INFO - Launching a standalone Selenium Server
2016-12-05 05:44:43.115:INFO::main: Logging initialized @12024ms
05:44:46.843 INFO - Driver provider org.openqa.selenium.ie.InternetExplorerDriver registration is skipped:
 registration capabilities Capabilities [{ensureCleanSession=true, browserName=internet explorer, version=, platform=WINDOWS}] does not match the current platform LINUX
05:44:46.844 INFO - Driver provider org.openqa.selenium.edge.EdgeDriver registration is skipped:
 registration capabilities Capabilities [{browserName=MicrosoftEdge, version=, platform=WINDOWS}] does not match the current platform LINUX
05:44:46.845 INFO - Driver class not found: com.opera.core.systems.OperaDriver
05:44:46.845 INFO - Driver provider com.opera.core.systems.OperaDriver registration is skipped:
Unable to create new instances on this machine.
05:44:46.846 INFO - Driver class not found: com.opera.core.systems.OperaDriver
05:44:46.846 INFO - Driver provider com.opera.core.systems.OperaDriver is not registered
05:44:46.892 INFO - Driver provider org.openqa.selenium.safari.SafariDriver registration is skipped:
 registration capabilities Capabilities [{browserName=safari, version=, platform=MAC}] does not match the current platform LINUX
2016-12-05 05:44:47.873:INFO:osjs.Server:main: jetty-9.2.15.v20160210
2016-12-05 05:44:49.230:INFO:osjsh.ContextHandler:main: Started o.s.j.s.ServletContextHandler@5dfcfece{/,null,AVAILABLE}
2016-12-05 05:44:50.414:INFO:osjs.ServerConnector:main: Started ServerConnector@482f8f11{HTTP/1.1}{0.0.0.0:4444}
2016-12-05 05:44:50.415:INFO:osjs.Server:main: Started @19325ms
05:44:50.418 INFO - Selenium Server is up and running
---
Stopping selenium13_selenium_1 ... 
Stopping selenium13_postgres_1 ... 
�[2B�[1A�[2K
Stopping selenium13_postgres_1 ... done
�[1BRemoving selenium13_selenium_1 ... 
Removing selenium13_galaxy_1 ... 
Removing selenium13_postgres_1 ... 
�[2B�[1A�[2K
Removing selenium13_postgres_1 ... done
�[1BRemoving network selenium13_default

@martenson martenson closed this Dec 8, 2016

@martenson martenson reopened this Dec 8, 2016

@martenson martenson closed this Dec 8, 2016

@martenson martenson reopened this Dec 8, 2016

@jmchilton

This comment has been minimized.

Copy link
Member Author

commented Dec 8, 2016

@martenson Are you working on this still? I think there might be a networking problem but I don't have shell access to the Jenkins worker as far as I can tell. Is docker network ls flooded with old docker-compose networks?

@martenson

This comment has been minimized.

Copy link
Member

commented Dec 8, 2016

@jmchilton I am trying to at least have it trigger and execute reliably, so we can test the other things without pulling our hair.

@jmchilton

This comment has been minimized.

Copy link
Member Author

commented Dec 8, 2016

https://jenkins.galaxyproject.org/job/selenium/22/console that one was working with lots of tests - just needed a longer timeout! 🎆

@martenson

This comment has been minimized.

Copy link
Member

commented Dec 8, 2016

@jmchilton yep, I killed the timeout immediately after I saw it.

@jmchilton

This comment has been minimized.

Copy link
Member Author

commented Dec 8, 2016

@martenson I've seen at least one run hang now - so I wouldn't kill the timeout, I'd just increase it to one hour if possible.

@jmchilton

This comment has been minimized.

Copy link
Member Author

commented Dec 8, 2016

@martenson Can you merge this - the Selenium tests don't work Jenkins yet but that is true regardless of this PR and I have ongoing work that depends on it.

@martenson martenson merged commit e3d1bd6 into galaxyproject:dev Dec 8, 2016

4 of 6 checks passed

default Build finished. No test results found.
Details
selenium test Build finished.
Details
api test Build finished. 243 tests run, 0 skipped, 0 failed.
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
framework test Build finished. 131 tests run, 0 skipped, 0 failed.
Details
toolshed test Build finished. 580 tests run, 0 skipped, 0 failed.
Details
@jmchilton

This comment has been minimized.

Copy link
Member Author

commented Dec 8, 2016

Thank you kindly @martenson!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.