I try running Sonarqube on my local machine (Win 11) , and if i execute this command in CommandPrompt
Terminal when i run the commands
nothing happens , and the logs is not helpful
2022-10-01 15:33:10,545 DEBUG - Starting WinSW in console mode
2022-10-01 15:34:17,211 DEBUG - Starting WinSW in console mode
2022-10-01 15:38:23,074 DEBUG - Starting WinSW in console mode
2022-10-01 15:38:24,726 DEBUG - Starting WinSW in console mode
2022-10-01 15:38:25,963 DEBUG - Starting WinSW in console mode
2022-10-01 15:38:27,206 DEBUG - Starting WinSW in console mode
2022-10-01 15:39:00,867 DEBUG - Starting WinSW in console mode
2022-10-01 15:40:51,881 DEBUG - Starting WinSW in console mode
2022-10-01 15:41:03,903 DEBUG - Starting WinSW in console mode
2022-10-01 15:41:07,547 DEBUG - Starting WinSW in console mode
2022-10-01 15:42:37,268 DEBUG - Starting WinSW in console mode
2022-10-01 15:45:47,009 DEBUG - Starting WinSW in console mode
2022-10-01 15:46:03,944 DEBUG - Starting WinSW in service mode
2022-10-01 16:05:31,653 DEBUG - Starting WinSW in console mode
2022-10-01 16:05:34,158 DEBUG - Starting WinSW in console mode
2022-10-01 16:05:41,056 DEBUG - Starting WinSW in service mode
2022-10-01 16:06:02,870 DEBUG - Starting WinSW in console mode
2022-10-01 16:15:43,116 DEBUG - Starting WinSW in console mode
2022-10-01 16:15:47,200 DEBUG - Starting WinSW in console mode
2022-10-01 16:15:48,263 DEBUG - Starting WinSW in console mode
2022-10-01 16:15:49,220 DEBUG - Starting WinSW in console mode
anyone know the problem why i cant run Solarqube on my machine?
Related
I am trying to run Terracotta server 10.11 from https://www.terracotta.org/downloads/ to connect it with Ehcache in my Spring boot application. But the problem is that when i run Terracotta server instance using the server\bin\start-tc-server.bat it does not give any error but put the server in DIAGNOSTIC state as shown in logs below.
2022-11-24 14:22:01,660 INFO - Terracotta 5.8.5, as of 2021-12-16 at 22:21:34 UTC (Revision 3695ab2f870d94491c564e87c266555a7d1c096b from UNKNOWN)
2022-11-24 14:22:01,660 INFO - Extensions:
2022-11-24 14:22:01,679 INFO - PID is 23344
2022-11-24 14:22:01,965 INFO - Did not find configuration directory at: C:\Users\user\terracotta\config
2022-11-24 14:22:01,965 INFO - Starting node from config file: C:\Users\user\Downloads\ehcache-clustered-3.10.0-kit\ehcache-clustered-3.10.0-kit\server\conf\cluster.cfg
2022-11-24 14:22:02,266 INFO - Found only one node information in config file: C:\Users\user\Downloads\ehcache-clustered-3.10.0-kit\ehcache-clustered-3.10.0-kit\server\conf\cluster.cfg
2022-11-24 14:22:02,267 INFO - Starting unconfigured node: default-node
2022-11-24 14:22:02,271 INFO - Bootstrapped nomad system with root: C:\Users\user\terracotta\config
2022-11-24 14:22:02,277 INFO - Startup configuration of the node:
client-lease-duration=150s
client-reconnect-window=120s
cluster-name=clustered
failover-priority=availability
offheap-resources=main\:512MB
stripe.1.node.1.bind-address=0.0.0.0
stripe.1.node.1.group-bind-address=0.0.0.0
stripe.1.node.1.group-port=9430
stripe.1.node.1.hostname=localhost
stripe.1.node.1.log-dir=%H/terracotta/logs
stripe.1.node.1.name=default-node
stripe.1.node.1.port=9410
stripe.1.stripe-name=default-stripe
2022-11-24 14:22:02,280 INFO - Logging directory is not set. Logging only to the console
2022-11-24 14:22:02,293 INFO - Available Max Runtime Memory: 1820MB
2022-11-24 14:22:02,314 INFO - Creating server nodeID: NodeID[localhost:9410]
2022-11-24 14:22:02,546 INFO - Initializing LeaseServiceProvider with default lease length of 150000 ms
2022-11-24 14:22:02,548 INFO - Initializing org.terracotta.lease.service.LeaseServiceProvider#4cf92ef3
2022-11-24 14:22:02,549 INFO - Initializing org.terracotta.client.message.tracker.OOOMessageHandlerProvider#40f5b3f9
2022-11-24 14:22:02,556 INFO - Registered MBean with name: DiagnosticRequestHandler
2022-11-24 14:22:02,557 INFO - Registered Diagnostic Service: org.terracotta.nomad.server.NomadServer
2022-11-24 14:22:02,557 INFO - Registered Diagnostic Service: org.terracotta.dynamic_config.api.service.DynamicConfigService
2022-11-24 14:22:02,558 INFO - Registered Diagnostic Service: org.terracotta.dynamic_config.api.service.TopologyService
2022-11-24 14:22:02,558 INFO - Initializing org.terracotta.diagnostic.server.DiagnosticServiceProvider#1bf35727
2022-11-24 14:22:02,561 INFO - Initializing org.terracotta.diagnostic.server.extensions.DiagnosticExtensionsServiceProvider#410ee45a
2022-11-24 14:22:02,804 INFO - Initializing org.terracotta.management.service.monitoring.MonitoringServiceProvider#65c7455b
2022-11-24 14:22:02,804 INFO - Initializing org.terracotta.platform.ServerInfoProvider#240d561b
2022-11-24 14:22:02,806 INFO - Registered dynamic configuration change handler for setting client-reconnect-window: org.terracotta.dynamic_config.server.service.handler.ClientReconnectWindowConfigChangeHandler#74d20602
2022-11-24 14:22:02,809 INFO - Registered dynamic configuration change handler for setting log-dir: org.terracotta.dynamic_config.server.service.handler.NodeLogDirChangeHandler#67c6fc00
2022-11-24 14:22:02,810 INFO - Registered dynamic configuration change handler for setting failover-priority: ConfigChangeHandler#accept()
2022-11-24 14:22:02,810 INFO - Registered dynamic configuration change handler for setting public-hostname: ConfigChangeHandler#accept()
2022-11-24 14:22:02,811 INFO - Registered dynamic configuration change handler for setting public-port: ConfigChangeHandler#accept()
2022-11-24 14:22:02,811 INFO - Registered dynamic configuration change handler for setting cluster-name: ConfigChangeHandler#accept()
2022-11-24 14:22:02,812 INFO - Registered dynamic configuration change handler for setting lock-context: ConfigChangeHandler#accept()
2022-11-24 14:22:02,812 INFO - Registered dynamic configuration change handler for setting logger-overrides: org.terracotta.dynamic_config.server.service.handler.LoggerOverrideConfigChangeHandler#3ba87843
2022-11-24 14:22:02,813 INFO - Registered dynamic configuration change handler for setting tc-properties: org.terracotta.dynamic_config.server.api.SelectingConfigChangeHandler#16df9889
2022-11-24 14:22:02,815 INFO - Initializing org.terracotta.dynamic_config.server.service.DynamicConfigServiceProvider#29ca0612
2022-11-24 14:22:02,815 INFO - Registering implementation-provided service com.tc.services.PlatformServiceProvider#16b645b2
2022-11-24 14:22:02,816 INFO - Registering implementation-provided service com.tc.services.EntityMessengerProvider#3c352805
2022-11-24 14:22:02,816 INFO - Initializing com.tc.objectserver.persistence.NullPlatformStorageServiceProvider#149f57c4
2022-11-24 14:22:02,818 INFO - Registering implementation-provided service com.tc.services.LocalMonitoringProducer#5baa3715
2022-11-24 14:22:02,830 INFO - Creating 4 worker comm threads for default-node - L2_L1
2022-11-24 14:22:02,910 INFO - Registering implementation-provided service com.tc.services.CommunicatorService#7d51aa32
2022-11-24 14:22:02,920 INFO - HealthChecker Started
2022-11-24 14:22:02,952 INFO - Started the server in diagnostic mode
2022-11-24 14:22:02,967 INFO - Server started as default-node
2022-11-24 14:22:02,959 INFO - Terracotta Server instance has started diagnostic listening on all interfaces (address:/0.0.0.0 port:9410)
2022-11-24 14:22:03,177 INFO - Moved to State[ DIAGNOSTIC ]
According to the documentation it should be in ACTIVE state to be running properly. Still i tried to make connection with the server from my Spring boot application but it was also unable to reach it and gave TimeoutException.
I am using the following command to run the server instance:
./start-tc-server.bat -f C:\Users\user\Downloads\ehcache-clustered-3.10.0-kit\ehcache-clustered-3.10.0-kit\server\conf\cluster.cfg
Does anyone have any clue why its not getting to ACTIVE state ? maybe try to run it on your end and see if the server gets to ACTIVE state. Or is there anything i am missing ?
Thanks in Advance.
P.S I tried running older version of Terracotta server from the same downloads page and it easily goes to active state but i cannot use old version since it is not compaitable with Ehcache 3.x
You need to activate the server.
In the kit that you downloaded navigate to /tools/bin and you need to run config-tool.bat activate -f ../../server/conf/cluster.cfg
This will create a folder C:\Users\{user}\terracotta that will contain the configs and logs for the terracotta server, so the next time you start it will use the configs in the folder and automatically go to activate state.
If you need to change configs delete the folder, restart terracotta and activate it again using the config tool.
I'm a newbie to Android Studio and I install Android Studio 2021.1.1 from scratch on Windows 10, but when I want to run the emulator, it just can't be launched with this error:
in the log located at C:\Users\xxx\AppData\Local\Google\AndroidStudio2021.1\log, I got some info as below. So can anyone help to figure it out?
2022-03-24 16:09:10,973 [ 826150] INFO - testKnownPluginVersionProvider - 'gradle' plugin missing from the offline Maven repo, will use default 7.1.2
2022-03-24 16:09:11,368 [ 826545] INFO - ativeWorkspaceModificationTask - NDK support for project 'Demo1' is disabled because the project doesn't contain any valid native configurations.
2022-03-24 16:09:27,095 [ 842272] WARN - vdmanager.AvdManagerConnection - Error setting permissions for C:\Users\xxx\temp\emu.tmp
2022-03-24 16:09:29,433 [ 844610] INFO - manager.EmulatorProcessHandler - Emulator: C:\Users\xxx\AppData\Local\Android\Sdk\emulator\emulator.exe -netdelay none -netspeed full -studio-params C:\Users\xxx\temp\emu.tmp -avd Nexus_6_API_30 -qt-hide-window -grpc-use-token -idle-grpc-timeout 300
2022-03-24 16:09:39,317 [ 854494] INFO - manager.EmulatorProcessHandler - Emulator: WARNING | Crash service did not start
2022-03-24 16:09:39,317 [ 854494] INFO - manager.EmulatorProcessHandler - Emulator:
2022-03-24 16:09:39,471 [ 854648] INFO - manager.EmulatorProcessHandler - Emulator: WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
2022-03-24 16:09:45,515 [ 860692] INFO - manager.EmulatorProcessHandler - Emulator: INFO | Android emulator version 31.2.9.0 (build_id 8316981) (CL:N/A)
2022-03-24 16:09:45,515 [ 860692] INFO - manager.EmulatorProcessHandler - Emulator: Process finished with exit code -1073741819 (0xC0000005)
2022-03-24 16:09:45,515 [ 860692] WARN - manager.EmulatorProcessHandler - Emulator terminated with exit code -1073741819
2022-03-24 16:09:55,157 [ 870334] WARN - com.intellij.util.xmlb.Binding - no accessors for com.intellij.openapi.updateSettings.impl.pluginsAdvertisement.PluginAdvertiserExtensionsStateService$State
2022-03-24 16:09:55,188 [ 870365] INFO - rationStore.ComponentStoreImpl - Saving appClangTidySettings took 16 ms, FileTypeManager took 15 ms, PluginFeatureService took 15 ms, VcsApplicationSettings took 16 ms
2022-03-24 16:09:55,701 [ 870878] INFO - rationStore.ComponentStoreImpl - Saving Project(name=Demo1, containerState=COMPONENT_CREATED, componentStore=C:\N-20L6PF1KPTJU-Data\xxx\Documents\99.Self.Learning\00.Android)XDebuggerManager took 30 ms
For the permission under C:\Users\xxx\temp*, it has no difference if I set it to full-control or read-only.
I don't know exactly what's the rc, but when I tried Nexus 6 API 28, it works.
I have installed Neo4j 2.3.2 Community Edition on Mac OS 10.10. I can launch the application and connect to it from localhost:7474/browser/. So far, so good.
I would like to launch Neo4j 2.3.2 from a Terminal window, so that I don't have the overhead of a windowed application running at the same time. When I run the following command...
$ ~/neo4j/bin/neo4j console
... I get this output in the Terminal window:
WARNING: Max 256 open files allowed, minimum of 40 000 recommended. See the Neo4j manual.
Starting Neo4j Server console-mode...
Unable to find any JVMs matching version "1.7".
Using additional JVM arguments: -server -XX:+DisableExplicitGC -Dorg.neo4j.server.properties=conf/neo4j-server.properties -Djava.util.logging.config.file=conf/logging.properties -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:-OmitStackTraceInFastThrow -XX:hashCode=5 -Dneo4j.ext.udc.source=tarball
2016-02-25 14:03:18.755+0000 INFO [API] Setting startup timeout to: 120000ms based on 120000
2016-02-25 14:03:58.356+0000 INFO [API] Successfully started database
2016-02-25 14:04:04.220+0000 INFO [API] Starting HTTP on port :7474 with 2 threads available
2016-02-25 14:04:13.512+0000 INFO [API] Enabling HTTPS on port :7473
09:04:20.201 [main] INFO org.eclipse.jetty.util.log - Logging initialized #98517ms
2016-02-25 14:04:23.034+0000 INFO [API] Mounting static content at [/webadmin] from [webadmin-html]
2016-02-25 14:04:25.785+0000 INFO [API] Mounting static content at [/browser] from [browser]
09:04:25.993 [main] INFO org.eclipse.jetty.server.Server - jetty-9.2.4.v20141103
09:04:26.722 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.h.MovedContextHandler#1611ba2{/,null,AVAILABLE}
09:04:27.794 [main] INFO o.e.j.w.StandardDescriptorProcessor - NO JSP Support for /webadmin, did not find org.apache.jasper.servlet.JspServlet
09:04:27.981 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.w.WebAppContext#132ea25{/webadmin,jar:file:/Users/james/neo4j/system/lib/neo4j-server-2.2.5-static-web.jar!/webadmin-html,AVAILABLE}
09:04:38.841 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler#60bfaa02{/db/manage,null,AVAILABLE}
09:04:39.326 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler#28e2e149{/db/data,null,AVAILABLE}
09:04:39.353 [main] INFO o.e.j.w.StandardDescriptorProcessor - NO JSP Support for /browser, did not find org.apache.jasper.servlet.JspServlet
09:04:39.355 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.w.WebAppContext#78e6aa71{/browser,jar:file:/Users/james/neo4j/system/lib/neo4j-browser-2.2.5.jar!/browser,AVAILABLE}
09:04:39.536 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler#4994d9ab{/,null,AVAILABLE}
09:04:39.745 [main] INFO o.e.jetty.server.ServerConnector - Started ServerConnector#2d19cf20{HTTP/1.1}{localhost:7474}
09:04:40.576 [main] INFO o.e.jetty.server.ServerConnector - Started ServerConnector#43c742c{SSL-HTTP/1.1}{localhost:7473}
09:04:40.577 [main] INFO org.eclipse.jetty.server.Server - Started #119058ms
2016-02-25 14:04:40.577+0000 INFO [API] Server started on: http://localhost:7474/
2016-02-25 14:04:40.590+0000 INFO [API] Remote interface ready and available at [http://localhost:7474/]
I have Java version 8, update 74 installed (build 1.8.0_74-b02), so I assume that I can ignore the warning Unable to find any JVMs matching version "1.7".
However, when I visit http://localhost:7474/ in Chrome Version 45.0.2454.85 (64-bit), I see three errors in the Developer Console: two files that fail to load and a subsequent script error.
localhost/:28 GET http://localhost:7474/browser/styles/68eddd94.main.css
localhost/:466 GET http://localhost:7474/browser/scripts/ded362b3.scripts.js
Uncaught Error: [$injector:modulerr] Failed to instantiate module neo4jApp due to:
Error: [$injector:nomod] Module 'neo4jApp' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.
As a result, the Neo4j interface does not appear in the browser window.
Is it possible to run Neo4j 2.3.2 from the Terminal, and if so, what do I need to do to get http://localhost:7474/ to load correctly?
Shift-reload, or test in an incognito window.
Looks like a JS file mismatch due to aggressive browser caching.
I'm trying to setup Teamcity on an EC2 Ubuntu instance.
I've:
Downloaded the package through wget http://download.jetbrains.com/teamcity/TeamCity-9.0.4.tar.gz. Unpackaged it.
Unpackaged it: tar -xvzf TeamCity-9.0.4.tar.gz.
sh Teamcity/bin/teamcity-server.sh start.
I can't access the web-app, and when I check the logs, says:
INFO - jetbrains.buildServer.STARTUP - Server shutdown has been requested
WARN - jetbrains.buildServer.STARTUP - Could not determine the local IP address: ip-172-30-1-83: ip-172-30-1-83: unknown error
INFO - jetbrains.buildServer.STARTUP - Server IP address: -unknown-
INFO - jetbrains.buildServer.STARTUP - Server shutdown complete
Complete log:
INFO - jetbrains.buildServer.STARTUP - Starting TeamCity server
INFO - jetbrains.buildServer.STARTUP - Server shutdown has been requested
INFO - jetbrains.buildServer.STARTUP - TeamCity version: 9.0.4 (build 32407), data format version 709
INFO - jetbrains.buildServer.STARTUP - OS: Linux, User: ubuntu, JRE: 1.8.0_45-b14 Java HotSpot(TM) 64-Bit Server VM
INFO - jetbrains.buildServer.STARTUP - JVM parameters: -Djava.util.logging.config.file=/home/ubuntu/TeamCity/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xmx512m -XX:MaxPermSize=270m -Dlog4j.configuration=file:/home/ubuntu/TeamCity/bin/../conf/teamcity-server-log4j.xml -Dteamcity_logs=../logs/ -Djsse.enableSNIExtension=false -Djava.awt.headless=true -Djava.endorsed.dirs=/home/ubuntu/TeamCity/endorsed -Dcatalina.base=/home/ubuntu/TeamCity -Dcatalina.home=/home/ubuntu/TeamCity -Djava.io.tmpdir=/home/ubuntu/TeamCity/temp
INFO - jetbrains.buildServer.STARTUP - Garbage collection: Copy, MarkSweepCompact
WARN - jetbrains.buildServer.STARTUP - Could not determine the local IP address: ip-172-30-1-83: ip-172-30-1-83: unknown error
INFO - jetbrains.buildServer.STARTUP - Web server version: Apache Tomcat/7.0.59
INFO - jetbrains.buildServer.STARTUP - Server IP address: -unknown-
INFO - jetbrains.buildServer.STARTUP - Servlet real path: /home/ubuntu/TeamCity/webapps/ROOT/
INFO - jetbrains.buildServer.STARTUP - Current stage: TeamCity server is shutting down
INFO - jetbrains.buildServer.STARTUP - Stopping the main application
INFO - jetbrains.buildServer.STARTUP - The main servlet is not initialized, nothing to shut down.
INFO - jetbrains.buildServer.STARTUP - Server shutdown complete
Any hints on how to solve it?
I have Teamcity's web-app working on my local machine (also Ubuntu, and the same Teamcity package).
Read the shell script TeamCity/bin/teamcity-server.sh, it is written with limitation, the script can't run out of the application folder.
export CATALINA_OPTS
CATALINA_HOME=./..
CATALINA_BASE=./..
So you should cd to the bin folder and run :
cd Teamcity/bin
sh teamcity-server.sh start
Let me know if it fixs your issue or not.
I'm getting problems where I can't get firefox to sync up with selenium when running automated tests. When I run the selenium server & the firefox phpunit tests, firefox continually times out (apparently) as it's unable to connect on the appropriate port. When I connect myself, I get some kind of jetty 403 error "forbidden for proxy", but I don't really know what to do to correct the issue.
How do I debug this to determine where the problem lies?
More detail on the logs and the error messages below:
I start the selenium server:
java -jar selenium-server-standalone-2.42.2.jar
Oct 20, 2014 2:44:09 PM org.openqa.grid.selenium.GridLauncher main
INFO: Launching a standalone server
14:44:09.957 INFO - Java: Oracle Corporation 25.25-b02
14:44:09.957 INFO - OS: Linux 3.2.0-70-generic amd64
14:44:09.964 INFO - v2.42.2, with Core v2.42.2. Built from revision 6a6995d
14:44:10.048 INFO - Default driver org.openqa.selenium.ie.InternetExplorerDriver registration is skipped: registration capabilities Capabilities [{ensureCleanSession=true, browserName=internet explorer, version=, platform=WINDOWS}] does not match with current platform: LINUX
14:44:10.086 INFO - RemoteWebDriver instances should connect to: http://127.0.0.1:4444/wd/hub
14:44:10.088 INFO - Version Jetty/5.1.x
14:44:10.089 INFO - Started HttpContext[/selenium-server,/selenium-server]
14:44:10.111 INFO - Started org.openqa.jetty.jetty.servlet.ServletHandler#725bef66
14:44:10.111 INFO - Started HttpContext[/wd,/wd]
14:44:10.111 INFO - Started HttpContext[/selenium-server/driver,/selenium-server/driver]
14:44:10.111 INFO - Started HttpContext[/,/]
14:44:10.115 INFO - Started SocketListener on 0.0.0.0:4444
14:44:10.115 INFO - Started org.openqa.jetty.jetty.Server#30dae81
Then I run the functional selenium tests for firefox as the www-data user:
sudo -u www-data ../../vendor/bin/phpunit -c refox.xml functional
PHPUnit 3.7.37 by Sebastian Bergmann.
Configuration read from /srv/xxx/protected/tests/firefox.xml
PHP Notice: Undefined offset: 1 in /srv/xxx/protected/extensions/webdriver-bindings/phpwebdriver/WebDriver.php on line 58
FCurrent URL: (Unknown)
Current Title: (Unknown)
Screenshot file: /srv/xxx/protected/tests/output/test.failed.1413831941.6997.png
Now, from what I can tell, the pertinent error from selenium is:
15:40:30.768 WARN - Exception: Unable to connect to host 127.0.0.1 on port 7055 after 45000 ms. Firefox console output:
#googlecode.com visible
1413833983888 DeferredSave.extensions.json DEBUG Save changes
1413833983889 DeferredSave.extensions.json DEBUG Save changes
1413833983889 addons.xpi DEBUG New add-on langpack-en-GB#firefox.mozilla.org installed in app-global
1413833983896 addons.xpi-utils DEBUG Make addon app-global:langpack-en-GB#firefox.mozilla.org visible
1413833983896 DeferredSave.extensions.json DEBUG Save changes
1413833983896 DeferredSave.extensions.json DEBUG Save changes
1413833983898 addons.xpi DEBUG New add-on {972ce4c6-7e08-4474-a285-3208198ce6fd} installed in app-global
1413833983900 addons.xpi-utils DEBUG Make addon app-global:{972ce4c6-7e08-4474-a285-3208198ce6fd} visible
1413833983900 DeferredSave.extensions.json DEBUG Save changes
1413833983900 DeferredSave.extensions.json DEBUG Save changes
1413833983900 addons.xpi DEBUG New add-on langpack-en-ZA#firefox.mozilla.org installed in app-global
1413833983906 addons.xpi-utils DEBUG Make addon app-global:langpack-en-ZA#firefox.mozilla.org visible
1413833983906 DeferredSave.extensions.json DEBUG Save changes
1413833983906 DeferredSave.extensions.json DEBUG Save changes
1413833983907 addons.xpi DEBUG New add-on ubufox#ubuntu.com installed in app-system-share
1413833983910 addons.xpi-utils DEBUG Make addon app-system-share:ubufox#ubuntu.com visible
1413833983910 DeferredSave.extensions.json DEBUG Save changes
1413833983910 DeferredSave.extensions.json DEBUG Save changes
1413833983915 addons.xpi DEBUG Updating database with changes to installed add-ons
1413833983915 addons.xpi-utils DEBUG Updating add-on states
1413833983916 addons.xpi-utils DEBUG Writing add-ons list
1413833983917 addons.xpi DEBUG Registering manifest for /usr/lib/firefox/browser/extensions/langpack-en-GB#firefox.mozilla.org.xpi
1413833983918 addons.xpi DEBUG Registering manifest for /usr/lib/firefox/browser/extensions/langpack-en-ZA#firefox.mozilla.org.xpi
1413833984887 DeferredSave.extensions.json DEBUG Starting timer
1413833984920 addons.manager DEBUG shutdown
1413833984921 DeferredSave.extensions.json DEBUG Starting write
1413833984922 addons.xpi DEBUG shutdown
1413833984922 addons.xpi-utils DEBUG shutdown
1413833984986 DeferredSave.extensions.json DEBUG Write succeeded
1413833984986 addons.xpi-utils DEBUG XPI Database saved, setting schema version preference to 16
1413833984986 addons.xpi DEBUG Notifying XPI shutdown observers
1413833984990 addons.manager DEBUG Async provider shutdown done
1413833985681 addons.manager DEBUG Loaded provider scope for resource://gre/modules/addons/XPIProvider.jsm: ["XPIProvider"]
1413833985682 addons.manager DEBUG Loaded provider scope for resource://gre/modules/LightweightThemeManager.jsm: ["LightweightThemeManager"]
1413833985685 addons.xpi DEBUG startup
1413833985686 addons.xpi INFO Mapping ubufox#ubuntu.com to /usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/ubufox#ubuntu.com
1413833985686 addons.xpi INFO Mapping langpack-en-GB#firefox.mozilla.org to /usr/lib/firefox/browser/extensions/langpack-en-GB#firefox.mozilla.org.xpi
1413833985686 addons.xpi INFO Mapping {972ce4c6-7e08-4474-a285-3208198ce6fd} to /usr/lib/firefox/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
1413833985687 addons.xpi INFO Mapping langpack-en-ZA#firefox.mozilla.org to /usr/lib/firefox/browser/extensions/langpack-en-ZA#firefox.mozilla.org.xpi
1413833985687 addons.xpi DEBUG Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous6261528948184700600webdriver-profile/extensions/webdriver-staging
1413833985687 addons.xpi INFO Mapping fxdriver#googlecode.com to /tmp/anonymous6261528948184700600webdriver-profile/extensions/fxdriver#googlecode.com
1413833985688 addons.xpi DEBUG checkForChanges
1413833985692 addons.xpi DEBUG No changes found
1413833985695 addons.xpi DEBUG Registering manifest for /usr/lib/firefox/browser/extensions/langpack-en-GB#firefox.mozilla.org.xpi
1413833985696 addons.xpi DEBUG Registering manifest for /usr/lib/firefox/browser/extensions/langpack-en-ZA#firefox.mozilla.org.xpi
*** Blocklist::_preloadBlocklistFile: blocklist is disabled
15:41:08.028 INFO - Executing: [new session: Capabilities [{nativeEvents=false, name=AmericaTest-firefox, browserName=firefox, javascriptEnabled=true, version=}]])
15:41:08.029 INFO - Creating a new session for Capabilities [{nativeEvents=false, name=AmericaTest-firefox, browserName=firefox, javascriptEnabled=true, version=}]
When I connect to 127.0.0.1:7055 manually in google chrome or firefox, it gets the error page:
HTTP ERROR: 403
Forbidden for Proxy
RequestURI=/
Powered by Jetty://
But I can connect to http://127.0.0.1:4444/wd/hub/ which shows this selenium widget
And hitting "create a session" creates a blank firefox page, just like the tests are doing.
So yeah, how do I force the firefox tests to use the appropriate port, and make sure that that proxying port is all set for selenium?
It seems that each release of Selenium only supports the latest stable version of Firefox. As stated below:
Each release of Selenium only supports Firefox N, N-1, ESR, & ESR-1 where N is the Firefox stable > channel at the time of release and ESR is the current ESR release. This means for Selenium 2.42 we > support Firefox 31 (N/ESR), 30 (N-1), 24 (ESR - 1). We should have the 2.43 release out within the > week, which will support 32 (N), 31 (N-1/ESR), 24 (ESR -1)
Have you tired to update Selenium or tried to use an older version of Firefox?