ARM hpi model can not simulate SVE instructions - arm

What i want to do is simulate SVE instruction included programs in gem5. But i failed. It stops at a ptrue instruction. below are the conditions of the test.
Program: Tower (which can be get in https://github.com/llvm/llvm-test-suite/tree/main/SingleSource/Benchmarks/Stanford)
Compiler: aarch64-linux-gnu-gcc
Compile flags: -O3 --static -march=armv8-a+sve
Gem5 run command ./build/ARM/gem5.opt -d ./se_results/$$test_prog ./configs/example/arm/starter_se.py --cpu="hpi" $$test_prog
I tried to debug gem5, here are the debug information:
27581250: system.cpu_cluster.cpus.execute.lsq.storeBuffer: StoreBuffer step numUnissuedAccesses: 0
27581250: system.cpu_cluster.cpus.execute: No interrupt controller
27581250: system.cpu_cluster.cpus.execute: [tid:0] thread_interrupted?=0 isInbetweenInsts?=1
27581250: system.cpu_cluster.cpus.execute: Attempting to issue [tid:0]
27581250: system.cpu_cluster.cpus.execute: Trying to issue inst: 0/437.569/2719/11034.12613 pc: 0x400e80 (ptrue) to FU: 0
27581250: system.cpu_cluster.cpus.execute: Can't issue as FU: 0 isn't capable
27581250: system.cpu_cluster.cpus.execute: Trying to issue inst: 0/437.569/2719/11034.12613 pc: 0x400e80 (ptrue) to FU: 1
27581250: system.cpu_cluster.cpus.execute: Can't issue as FU: 1 isn't capable
27581250: system.cpu_cluster.cpus.execute: Trying to issue inst: 0/437.569/2719/11034.12613 pc: 0x400e80 (ptrue) to FU: 2
27581250: system.cpu_cluster.cpus.execute: Can't issue as FU: 2 isn't capable
27581250: system.cpu_cluster.cpus.execute: Trying to issue inst: 0/437.569/2719/11034.12613 pc: 0x400e80 (ptrue) to FU: 3
27581250: system.cpu_cluster.cpus.execute: Can't issue as FU: 3 isn't capable
27581250: system.cpu_cluster.cpus.execute: Trying to issue inst: 0/437.569/2719/11034.12613 pc: 0x400e80 (ptrue) to FU: 4
27581250: system.cpu_cluster.cpus.execute: Can't issue as FU: 4 isn't capable
27581250: system.cpu_cluster.cpus.execute: Trying to issue inst: 0/437.569/2719/11034.12613 pc: 0x400e80 (ptrue) to FU: 5
27581250: system.cpu_cluster.cpus.execute: Can't issue as FU: 5 isn't capable
27581250: system.cpu_cluster.cpus.execute: Trying to issue inst: 0/437.569/2719/11034.12613 pc: 0x400e80 (ptrue) to FU: 6
27581250: system.cpu_cluster.cpus.execute: Can't issue as FU: 6 isn't capable
27581250: system.cpu_cluster.cpus.execute: Didn't issue inst: 0/437.569/2719/11034.12613 pc: 0x400e80 (ptrue)
After a few repetitions, the program gets stuck here.
I think maybe some SVM-based FUs r not enabled which caused this problem. But i don't know how to enable them.

Related

Selenium grid 4 : Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure error

Trying to set up selenium 4 grid with the below docker-compose file but getting the "Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure" error and need some help to fix the same.
docker-compose file:
# To execute this docker-compose yml file use `docker-compose -f docker-compose-v3-full-grid.yml up`
# Add the `-d` flag at the end for detached execution
# To stop the execution, hit Ctrl+C, and then `docker-compose -f docker-compose-v3-full-grid.yml down`
version: "3"
services:
selenium-event-bus:
image: selenium/event-bus:4.0.0-20211013
container_name: selenium-event-bus
ports:
- "4442:4442"
- "4443:4443"
- "5557:5557"
selenium-sessions:
image: selenium/sessions:4.0.0-20211013
container_name: selenium-sessions
ports:
- "5556:5556"
depends_on:
- selenium-event-bus
environment:
- SE_EVENT_BUS_HOST=selenium-event-bus
- SE_EVENT_BUS_PUBLISH_PORT=4442
- SE_EVENT_BUS_SUBSCRIBE_PORT=4443
selenium-session-queue:
image: selenium/session-queue:4.0.0-20211013
container_name: selenium-session-queue
ports:
- "5559:5559"
depends_on:
- selenium-event-bus
environment:
- SE_EVENT_BUS_HOST=selenium-event-bus
- SE_EVENT_BUS_PUBLISH_PORT=4442
- SE_EVENT_BUS_SUBSCRIBE_PORT=4443
selenium-distributor:
image: selenium/distributor:4.0.0-20211013
container_name: selenium-distributor
ports:
- "5553:5553"
depends_on:
- selenium-event-bus
- selenium-sessions
- selenium-session-queue
environment:
- SE_EVENT_BUS_HOST=selenium-event-bus
- SE_EVENT_BUS_PUBLISH_PORT=4442
- SE_EVENT_BUS_SUBSCRIBE_PORT=4443
- SE_SESSIONS_MAP_HOST=selenium-sessions
- SE_SESSIONS_MAP_PORT=5556
- SE_SESSION_QUEUE_HOST=selenium-session-queue
- SE_SESSION_QUEUE_PORT=5559
selenium-router:
image: selenium/router:4.0.0-20211013
container_name: selenium-router
ports:
- "4444:4444"
depends_on:
- selenium-distributor
- selenium-sessions
- selenium-session-queue
environment:
- SE_DISTRIBUTOR_HOST=selenium-distributor
- SE_DISTRIBUTOR_PORT=5553
- SE_SESSIONS_MAP_HOST=selenium-sessions
- SE_SESSIONS_MAP_PORT=5556
- SE_SESSION_QUEUE_HOST=selenium-session-queue
- SE_SESSION_QUEUE_PORT=5559
chrome:
image: selenium/node-chrome:4.0.0-20211013
shm_size: 2gb
depends_on:
- selenium-event-bus
environment:
- SE_EVENT_BUS_HOST=selenium-event-bus
- SE_EVENT_BUS_PUBLISH_PORT=4442
- SE_EVENT_BUS_SUBSCRIBE_PORT=4443
ports:
- "6900:5900"
Run command:
mvn clean install
This will trigger the execution of one cucumber test scenario thru the test runner mentioned in the testing.xml file.
It looks like the setup is pretty much completed and the logs here:
0.3s
dhamo#Dhamo-Mac expressqa_ecom_web % docker-compose -f docker-compose-v3-full-grid.yml up
[+] Running 7/7
⠿ Network expressqa_ecom_web_default Created 0.1s
⠿ Container selenium-event-bus Started 3.5s
⠿ Container expressqa_ecom_web_chrome_1 Started 5.3s
⠿ Container selenium-session-queue Started 4.7s
⠿ Container selenium-sessions Started 5.2s
⠿ Container selenium-distributor Started 5.6s
⠿ Container selenium-router Started 6.4s
Attaching to chrome_1, selenium-distributor, selenium-event-bus, selenium-router, selenium-session-queue, selenium-sessions
selenium-distributor | 2021-10-18 21:02:16,505 INFO spawned: 'selenium-grid-distributor' with pid 20
selenium-distributor | Starting Selenium Grid Distributor...
selenium-distributor | 2021-10-18 21:02:16,682 INFO success: selenium-grid-distributor entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
selenium-router | 2021-10-18 21:02:17,426 INFO Included extra file "/etc/supervisor/conf.d/selenium-grid-router.conf" during parsing
selenium-router | 2021-10-18 21:02:17,434 INFO supervisord started with pid 12
chrome_1 | Configuring server...
chrome_1 | Setting up SE_NODE_HOST...
chrome_1 | Setting up SE_NODE_PORT...
chrome_1 | Setting up SE_NODE_GRID_URL...
selenium-router | 2021-10-18 21:02:18,447 INFO spawned: 'selenium-grid-router' with pid 18
selenium-router | Starting Selenium Grid Router...
selenium-router | 2021-10-18 21:02:18,607 INFO success: selenium-grid-router entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
chrome_1 | Selenium Grid Node configuration:
chrome_1 | [events]
chrome_1 | publish = "tcp://selenium-event-bus:4442"
chrome_1 | subscribe = "tcp://selenium-event-bus:4443"
chrome_1 |
chrome_1 | [node]
chrome_1 | session-timeout = "300"
chrome_1 | override-max-sessions = false
chrome_1 | detect-drivers = false
chrome_1 | max-sessions = 1
chrome_1 |
chrome_1 | [[node.driver-configuration]]
chrome_1 | display-name = "chrome"
chrome_1 | stereotype = '{"browserName": "chrome", "browserVersion": "94.0", "platformName": "Linux"}'
chrome_1 | max-sessions = 1
chrome_1 |
chrome_1 | Starting Selenium Grid Node...
selenium-event-bus | 21:02:19.503 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
selenium-session-queue | 21:02:19.845 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
selenium-event-bus | 21:02:20.194 INFO [BoundZmqEventBus.<init>] - XPUB binding to [binding to tcp://*:4442, advertising as tcp://172.24.0.2:4442], XSUB binding to [binding to tcp://*:4443, advertising as tcp://172.24.0.2:4443]
selenium-sessions | 21:02:20.568 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
selenium-sessions | 21:02:20.828 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
selenium-event-bus | 21:02:21.517 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://172.24.0.2:4442 and tcp://172.24.0.2:4443
selenium-event-bus | 21:02:22.199 INFO [UnboundZmqEventBus.<init>] - Sockets created
selenium-sessions | 21:02:22.602 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://selenium-event-bus:4442 and tcp://selenium-event-bus:4443
selenium-event-bus | 21:02:23.238 INFO [UnboundZmqEventBus.<init>] - Event bus ready
selenium-session-queue | 21:02:23.839 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
selenium-distributor | 21:02:23.759 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
selenium-sessions | 21:02:23.971 INFO [UnboundZmqEventBus.<init>] - Sockets created
selenium-distributor | 21:02:23.987 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
selenium-sessions | 21:02:25.028 INFO [UnboundZmqEventBus.<init>] - Event bus ready
selenium-session-queue | 21:02:25.443 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://selenium-event-bus:4442 and tcp://selenium-event-bus:4443
selenium-distributor | 21:02:25.711 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://selenium-event-bus:4442 and tcp://selenium-event-bus:4443
selenium-router | 21:02:25.948 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
selenium-router | 21:02:26.012 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
selenium-session-queue | 21:02:26.349 INFO [UnboundZmqEventBus.<init>] - Sockets created
selenium-distributor | 21:02:26.883 INFO [UnboundZmqEventBus.<init>] - Sockets created
selenium-event-bus | 21:02:27.149 INFO [BaseServerOptions.lambda$getExternalUri$0] - No network connection, guessing name: 13687f81574b
selenium-session-queue | 21:02:27.419 INFO [UnboundZmqEventBus.<init>] - Event bus ready
selenium-event-bus | 21:02:27.508 WARN [MacAddressUtil.defaultMachineId] - Failed to find a usable hardware address from the network interfaces; using random bytes: c4:5c:a7:6e:6e:8d:0a:e3
selenium-distributor | 21:02:27.932 INFO [UnboundZmqEventBus.<init>] - Event bus ready
chrome_1 | 21:02:28.316 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
chrome_1 | 21:02:28.394 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
selenium-event-bus | 21:02:28.417 INFO [EventBusCommand.execute] - Started Selenium EventBus 4.0.0 (revision 3a21814679): http://13687f81574b:5557
selenium-session-queue | 21:02:28.435 INFO [BaseServerOptions.lambda$getExternalUri$0] - No network connection, guessing name: 9d9b6ded1846
selenium-sessions | 21:02:28.624 INFO [BaseServerOptions.lambda$getExternalUri$0] - No network connection, guessing name: 7dbac3cddaa7
selenium-session-queue | 21:02:28.872 WARN [MacAddressUtil.defaultMachineId] - Failed to find a usable hardware address from the network interfaces; using random bytes: 28:9e:a1:e5:f8:f2:8f:d6
selenium-sessions | 21:02:28.929 WARN [MacAddressUtil.defaultMachineId] - Failed to find a usable hardware address from the network interfaces; using random bytes: 83:83:18:81:93:d2:80:1b
selenium-sessions | 21:02:29.453 INFO [SessionMapServer.execute] - Started Selenium SessionMap 4.0.0 (revision 3a21814679): http://7dbac3cddaa7:5556
selenium-session-queue | 21:02:29.551 INFO [NewSessionQueueServer.execute] - Started Selenium SessionQueue 4.0.0 (revision 3a21814679): http://9d9b6ded1846:5559
chrome_1 | 21:02:29.976 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://selenium-event-bus:4442 and tcp://selenium-event-bus:4443
chrome_1 | 21:02:30.655 INFO [UnboundZmqEventBus.<init>] - Sockets created
chrome_1 | 21:02:31.736 INFO [UnboundZmqEventBus.<init>] - Event bus ready
selenium-router | 21:02:32.709 INFO [BaseServerOptions.lambda$getExternalUri$0] - No network connection, guessing name: 8885bd19bf09
chrome_1 | 21:02:32.908 INFO [BaseServerOptions.lambda$getExternalUri$0] - No network connection, guessing name: 8646325b6e37
chrome_1 | 21:02:32.943 INFO [NodeServer.createHandlers] - Reporting self as: http://8646325b6e37:5555
chrome_1 | 21:02:32.989 INFO [BaseServerOptions.lambda$getExternalUri$0] - No network connection, guessing name: 8646325b6e37
chrome_1 | 21:02:33.441 INFO [NodeOptions.getSessionFactories] - Detected 4 available processors
selenium-distributor | 21:02:33.943 INFO [BaseServerOptions.lambda$getExternalUri$0] - No network connection, guessing name: d8e53d166441
selenium-distributor | 21:02:35.974 WARN [MacAddressUtil.defaultMachineId] - Failed to find a usable hardware address from the network interfaces; using random bytes: e1:2b:2f:38:b2:02:67:c4
chrome_1 | 21:02:36.783 INFO [NodeOptions.report] - Adding chrome for {"browserVersion": "94.0","browserName": "chrome","platformName": "Linux","se:vncEnabled": true} 1 times
selenium-distributor | 21:02:45.369 INFO [DistributorServer.execute] - Started Selenium Distributor 4.0.0 (revision 3a21814679): http://d8e53d166441:5553
chrome_1 | 21:02:46.857 INFO [Node.<init>] - Binding additional locator mechanisms: id, name, relative
selenium-distributor | /opt/bin/start-selenium-grid-distributor.sh: line 66: 24 Killed java ${JAVA_OPTS} -jar /opt/selenium/selenium-server.jar distributor --sessions-host "${SE_SESSIONS_MAP_HOST}" --sessions-port "${SE_SESSIONS_MAP_PORT}" --sessionqueue-host "${SE_SESSION_QUEUE_HOST}" --sessionqueue-port "${SE_SESSION_QUEUE_PORT}" --publish-events tcp://"${SE_EVENT_BUS_HOST}":"${SE_EVENT_BUS_PUBLISH_PORT}" --subscribe-events tcp://"${SE_EVENT_BUS_HOST}":"${SE_EVENT_BUS_SUBSCRIBE_PORT}" --bind-bus false ${HOST_CONFIG} ${PORT_CONFIG} ${SE_OPTS}
selenium-distributor | 2021-10-18 21:02:50,661 INFO exited: selenium-grid-distributor (exit status 137; not expected)
chrome_1 | 21:02:51.371 INFO [BaseServerOptions.lambda$getExternalUri$0] - No network connection, guessing name: 8646325b6e37
chrome_1 | 21:02:51.513 WARN [MacAddressUtil.defaultMachineId] - Failed to find a usable hardware address from the network interfaces; using random bytes: 9f:65:82:c3:22:f7:b7:d4
chrome_1 | 21:02:51.757 INFO [NodeServer$1.start] - Starting registration process for node id adb8ff56-c40d-4d5b-8298-01df3135a951
selenium-router | 21:02:51.758 INFO [BaseServerOptions.lambda$getExternalUri$0] - No network connection, guessing name: 8885bd19bf09
chrome_1 | 21:02:51.769 INFO [NodeServer.execute] - Started Selenium node 4.0.0 (revision 3a21814679): http://8646325b6e37:5555
chrome_1 | 21:02:51.797 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
selenium-router | 21:02:52.642 WARN [MacAddressUtil.defaultMachineId] - Failed to find a usable hardware address from the network interfaces; using random bytes: 74:60:3b:79:d9:3b:52:1e
selenium-router | 21:02:52.800 INFO [RouterServer.execute] - Started Selenium Router 4.0.0 (revision 3a21814679): http://8885bd19bf09:4444
chrome_1 | 21:03:01.893 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
chrome_1 | 21:03:11.927 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
Complete error logs while running one test:
org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
System info: host: 'Dhamo-Mac.local', ip: 'fe80:0:0:0:84c:43e7:38de:c02b%en0', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '11.6', java.version: '11.0.12'
Driver info: driver.version: RemoteWebDriver
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:573)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:213)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:131)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:144)
at core.DriverManager.createRemoteDriver(DriverManager.java:82)
at core.DriverManager.createDriver(DriverManager.java:44)
at core.DriverManager.getDriver(DriverManager.java:34)
at core.CoreBase.<init>(CoreBase.java:10)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
at org.picocontainer.injectors.AbstractInjector.newInstance(AbstractInjector.java:145)
at org.picocontainer.injectors.ConstructorInjector$1.run(ConstructorInjector.java:342)
at org.picocontainer.injectors.AbstractInjector$ThreadLocalCyclicDependencyGuard.observe(AbstractInjector.java:270)
at org.picocontainer.injectors.ConstructorInjector.getComponentInstance(ConstructorInjector.java:364)
at org.picocontainer.injectors.AbstractInjectionFactory$LifecycleAdapter.getComponentInstance(AbstractInjectionFactory.java:56)
at org.picocontainer.behaviors.AbstractBehavior.getComponentInstance(AbstractBehavior.java:64)
at org.picocontainer.behaviors.Stored.getComponentInstance(Stored.java:91)
at org.picocontainer.DefaultPicoContainer.getInstance(DefaultPicoContainer.java:699)
at org.picocontainer.DefaultPicoContainer.getComponent(DefaultPicoContainer.java:647)
at org.picocontainer.DefaultPicoContainer.getComponent(DefaultPicoContainer.java:632)
at org.picocontainer.parameters.BasicComponentParameter$1.resolveInstance(BasicComponentParameter.java:118)
at org.picocontainer.parameters.ComponentParameter$1.resolveInstance(ComponentParameter.java:136)
at org.picocontainer.injectors.SingleMemberInjector.getParameter(SingleMemberInjector.java:78)
at org.picocontainer.injectors.ConstructorInjector$CtorAndAdapters.getParameterArguments(ConstructorInjector.java:309)
at org.picocontainer.injectors.ConstructorInjector$1.run(ConstructorInjector.java:335)
at org.picocontainer.injectors.AbstractInjector$ThreadLocalCyclicDependencyGuard.observe(AbstractInjector.java:270)
at org.picocontainer.injectors.ConstructorInjector.getComponentInstance(ConstructorInjector.java:364)
at org.picocontainer.injectors.AbstractInjectionFactory$LifecycleAdapter.getComponentInstance(AbstractInjectionFactory.java:56)
at org.picocontainer.behaviors.AbstractBehavior.getComponentInstance(AbstractBehavior.java:64)
at org.picocontainer.behaviors.Stored.getComponentInstance(Stored.java:91)
at org.picocontainer.DefaultPicoContainer.getInstance(DefaultPicoContainer.java:699)
at org.picocontainer.DefaultPicoContainer.getComponent(DefaultPicoContainer.java:647)
at org.picocontainer.DefaultPicoContainer.getComponent(DefaultPicoContainer.java:678)
at io.cucumber.picocontainer.PicoFactory.getInstance(PicoFactory.java:49)
at io.cucumber.java.AbstractGlueDefinition.invokeMethod(AbstractGlueDefinition.java:47)
at io.cucumber.java.JavaHookDefinition.execute(JavaHookDefinition.java:59)
at io.cucumber.core.runner.CoreHookDefinition.execute(CoreHookDefinition.java:46)
at io.cucumber.core.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:21)
at io.cucumber.core.runner.ExecutionMode$1.execute(ExecutionMode.java:10)
at io.cucumber.core.runner.TestStep.executeStep(TestStep.java:92)
at io.cucumber.core.runner.TestStep.run(TestStep.java:64)
at io.cucumber.core.runner.TestCase.run(TestCase.java:110)
at io.cucumber.core.runner.Runner.runPickle(Runner.java:73)
at io.cucumber.testng.TestNGCucumberRunner.lambda$runScenario$0(TestNGCucumberRunner.java:117)
at io.cucumber.core.runtime.CucumberExecutionContext.runTestCase(CucumberExecutionContext.java:117)
at io.cucumber.testng.TestNGCucumberRunner.runScenario(TestNGCucumberRunner.java:114)
at io.cucumber.testng.AbstractTestNGCucumberTests.runScenario(AbstractTestNGCucumberTests.java:31)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:133)
at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:598)
at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:173)
at org.testng.internal.TestMethodWithDataProviderMethodWorker.call(TestMethodWithDataProviderMethodWorker.java:77)
at org.testng.internal.TestMethodWithDataProviderMethodWorker.call(TestMethodWithDataProviderMethodWorker.java:15)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.io.IOException: unexpected end of stream on Connection{localhost:4444, proxy=DIRECT hostAddress=localhost/0:0:0:0:0:0:0:1:4444 cipherSuite=none protocol=http/1.1}
at okhttp3.internal.http1.Http1Codec.readResponseHeaders(Http1Codec.java:208)
at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:88)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at org.openqa.selenium.remote.internal.OkHttpClient$Factory$1.lambda$createClient$1(OkHttpClient.java:152)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:45)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:126)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:200)
at okhttp3.RealCall.execute(RealCall.java:77)
at org.openqa.selenium.remote.internal.OkHttpClient.execute(OkHttpClient.java:103)
at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:105)
at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:74)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:136)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:552)
... 63 more
Caused by: java.io.EOFException: \n not found: limit=0 content=…
at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:237)
at okhttp3.internal.http1.Http1Codec.readHeaderLine(Http1Codec.java:215)
at okhttp3.internal.http1.Http1Codec.readResponseHeaders(Http1Codec.java:189)
... 86 more
Alternatively, when I try to open the hub url, I get the following:
It's how the remote driver object gets called.
case CHROME:
ChromeOptions options = getChromeOptions();
try {
driver = new RemoteWebDriver(new URL("http://localhost:4444"), options);
} catch (MalformedURLException e) {
e.printStackTrace();
}
Laptop config:
Mac m1 512GB
How can I possibly get rid of the issue?
As per this issue, the support is not there for M1 architecture yet and until they provide it, the issue will occur.

Flink 1.10.0 - The heartbeat of ResourceManager with id xxxx timed out

I am running flink standalone cluster HA in kubernetes. The same setup runs perfectly when using Flink 1.9 but getting below error continuously when using Flink 1.10.
INFO org.apache.flink.runtime.taskexecutor.TaskExecutor - The heartbeat of ResourceManager with id 783439e4ead380c60498e32a8e1c0ce3 timed out.
DEBUG org.apache.flink.runtime.taskexecutor.TaskExecutor - Close ResourceManager connection 783439e4ead380c60498e32a8e1c0ce3.
org.apache.flink.runtime.taskexecutor.exceptions.TaskManagerException: The heartbeat of ResourceManager with id 783439e4ead380c60498e32a8e1c0ce3 timed out.
at org.apache.flink.runtime.taskexecutor.TaskExecutor$ResourceManagerHeartbeatListener.notifyHeartbeatTimeout(TaskExecutor.java:1842)
at org.apache.flink.runtime.heartbeat.HeartbeatMonitorImpl.run(HeartbeatMonitorImpl.java:109)
flink-conf.yaml :
jobmanager.rpc.address: xx.xxx.xx.xxx
jobmanager.rpc.port: 6123
jobmanager.heap.size: 1500m
taskmanager.memory.process.size: 4000m
taskmanager.numberOfTaskSlots: 1
parallelism.default: 1
jobmanager.execution.failover-strategy: region
state.backend: filesystem
state.checkpoints.dir: file:///checkpoints
state.savepoints.dir: file:///savepoints
high-availability: zookeeper
high-availability.jobmanager.port: 50010
high-availability.zookeeper.quorum: xx.xx.xx.xx:xxxx
high-availability.zookeeper.path.root: /flink
high-availability.cluster-id: /ABCD
high-availability.storageDir: file:///recovery
heartbeat.interval: 60000
heartbeat.timeout: 60000
taskmanager.debug.memory.log: true
taskmanager.debug.memory.log-interval: 10000
taskmanager.memory.managed.fraction: 0.1
blob.server.port: 6124
query.server.port: 6125

can not invoke chromedriver on Linux (debian) machine

Resources: VM -Debian Linux , Selenium 4 , Chrome V78, ChromeDriver , Jenkins , Maven, JAVA 8
**Issue:** I can not invoke chromedriver on Linux (debian) machine.
I can see message "Please protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code."
on Jenkins.
Maven command : clean install test
Log Trace:::
[JENKINS REMOTING CAPACITY]===>channel started
Executing Maven: -B -f /var/lib/jenkins/workspace/Maven/pom.xml clean install test
[INFO] Scanning for projects...
[WARNING]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) # Land ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 8 source files to /var/lib/jenkins/workspace/Maven/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M3:test (default-test) # Land ---
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running TestSuite
[INFO ] 2019-09-18 21:51:26.644 [main] BaseClass - [32mINFO[m - Creating Screenshot folder for this current execution.
directory is : /var/lib/jenkins/workspace/Maven/screenshots
directory is exist /var/lib/jenkins/workspace/Maven/logs
directory is exist /var/lib/jenkins/workspace/Maven/test-output
[INFO ] 2019-09-18 21:51:26.655 [main] SetUpTest - [32mINFO[m - ============================================================
[INFO ] 2019-09-18 21:51:26.655 [main] SetUpTest - [32mINFO[m - ====== Initializing Driver, Starting Browser Session =========
[INFO ] 2019-09-18 21:51:26.655 [main] SetUpTest - [32mINFO[m - ============================================================
projectPath is: /var/lib/jenkins/workspace/Maven
[INFO ] 2019-09-18 21:51:26.656 [main] BaseClass - [32mINFO[m - projectPath is: /var/lib/jenkins/workspace/Maven
[INFO ] 2019-09-18 21:51:26.656 [main] BaseClass - [32mINFO[m - Driver value is : null
[INFO ] 2019-09-18 21:51:26.656 [main] BaseClass - [32mINFO[m - chrome driver is here
Starting ChromeDriver 78.0.3904.11 (eaaae9de6b8999773fa33f92ce1e1bbe294437cf-refs/branch-heads/3904#{#86}) on port 4878
Only local connections are allowed.
**Please protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code.**
[INFO ] 2019-09-18 21:51:27.930 [main] SetUpTest -
[INFO ] 2019-09-18 21:51:27.930 [main] SetUpTest - ============ createAccount Test case is Started. ==============
[INFO ] 2019-09-18 21:51:27.931 [main] SetUpTest -
[INFO ] 2019-09-18 21:51:27.932 [main] TestListener -
[INFO ] 2019-09-18 21:51:27.933 [main] TestListener - ===== createAccount - Test case is Skipped =======
[INFO ] 2019-09-18 21:51:27.934 [main] TestListener -
[INFO ] 2019-09-18 21:51:27.934 [main] TestListener - ===== createAccount - Test case is Failed =======
[INFO ] 2019-09-18 21:51:27.941 [main] BaseClass - ******** Disposing Browser Driver **********
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[ERROR] There are test failures. This is the final result
----------------------------------------------------------------
**My code :**
This is my Selenium code:
if (browserName.equalsIgnoreCase("chrome")) {
System.setProperty("webdriver.chrome.driver", "/usr/bin/chromedriver");
ChromeOptions options = new ChromeOptions();
options.addArguments("--verbose");
options.addArguments("--whitelisted-ips=''");
options.addArguments("--disable-extensions");
options.addArguments("--disable-notifications");
options.addArguments("disable-infobars");
options.addArguments("--incognito");
options.addArguments("--disable-gpu");
options.addArguments("--no-sandbox");
options.addArguments("--disable-gpu --disable-software-rasterizer");
options.addArguments("--disable-gpu-sandbox");
options.addArguments("--disable-features=VizDisplayCompositor");
These are options I have tried on chromedriver so far
driver = new ChromeDriver(options); // This line is not being invoked successfully.
------------------------------------------
What I tried so far:
1. I tried firefox browser - which is not launching as well
2. I tried to "chmod 777" files, drivers and folders as per requirement
3. I set up few chrome "options.addArguments" to "disbale GPU" , "headless" and "no sandbox" as per google
4. I looked in VM that if there are already multiple instance opened for Chromedriver via "htop" and other commands to kill the older sessions but I did not see any chrome because it's never been launched
5. https://stgconsulting.com/running-automated-selenium-tests-from-jenkins-on-linux/
6. https://tecadmin.net/setup-selenium-chromedriver-on-ubuntu
Resources: Maven, Chrome,ChromeDriver, Linux(Debian), Java, Testng, jenkins
Link I followed for basic Linux (Debian) set up : https://stgconsulting.com/running-automated-selenium-tests-from-jenkins-on-linux/
Before solution we have been seeing this below error:
[INFO ] 2019-09-20 09:41:19.341 [main] BaseClass - browserName value is : chrome
[INFO ] 2019-09-20 09:41:19.341 [main] BaseClass - chrome driver is here
Starting ChromeDriver 78.0.3904.11 (eaaae9de6b8999773fa33f92ce1e1bbe294437cf-refs/branch-heads/3904#{#86}) on port 29688
Only local connections are allowed.
Please protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code.
[INFO ] 2019-09-20 09:41:23.904 [main] SetUpTest - ==========================================================
[INFO ] 2019-09-20 09:41:23.904 [main] SetUpTest - =========== createAccount Test case is Started.
After solution I am not seeing failure/error and I am able to execute lest on Linux (Debian):
[INFO ] 2019-09-20 08:46:30.675 [main] BaseClass - chrome driver is here
Starting ChromeDriver 75.0.3770.140 (2d9f97485c7b07dc18a74666574f19176731995c-refs/branch-heads/3770#{#1155}) on port 9770
Only local connections are allowed.
Please protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code.
[1568994392.814][WARNING]: This version of ChromeDriver has not been tested with Chrome version 76.
Sep 20, 2019 8:46:33 AM org.openqa.selenium.remote.ProtocolHandshake createSession
INFO: Detected dialect: W3C
[INFO ] 2019-09-20 08:46:33.227 [main] BaseClass - Browser is Chrome
solution steps and information:
(1) You can have latest Chrome Linux Browser on your box
(2) Go here https://chromedriver.chromium.org/downloads and do bruteforce of ChromeDriver versions
(3) I am using Chrome linux 77 (as of now 9/20/2019) and chromedriver 76.0.3809.25 , worked for me
(4) "Please protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code" - got nothing with firewall
(5) Check your Chmod 777 permission for chromeDriver
It's a BROWSER AND CHROME DRIVER MISMTACH , ALL YOU NEED TO DO IS TO CHECK THE COMPATIBILITY

Corrupted files with Camel Ftp component

I'm using apache camel to make a ftp client for downloading some files to some local directory. The program reads a xml file to get the name of the file that will be fetched from the ftp.The program seems to work except that the files downloaded are corrupted. Right now I'm trying to download some image files but the ones I get are 14.9Kb and corrupted, no error message shown.
This is my code:
main
public void main() throws FileNotFoundException {
BasicConfigurator.configure();
RutaFtp routeBuilder = new RutaFtp();
CamelContext ctx = new DefaultCamelContext();
try {
ctx.addRoutes(routeBuilder);
ctx.start();
Thread.sleep(10000);
ctx.stop();
}
catch (Exception e) {
e.printStackTrace();
}
}
camel route:
from("file:./?fileName=Datos.xml&noop=true")
.split(xpath("//Datos/imagen/text()"))
.setProperty("rutaArchivo", this.body())
.log(LoggingLevel.INFO, "imagen: ${body}")
.process(ExtraerNombre).to("direct:ftp").end();
from("direct:ftp")
.pollEnrich("ftp://"+user+"#"+ftp+"/?password="+password+"&recursive=true&passiveMode=true&fileName=${body}&delete="+borrado+"")
.to("file:C:/outputFolder?flatten=true").end();
}
I've tried using the streamDownload parameter but tha prevents the files to be downloaded (I don't know why)
.pollEnrich("ftp://"+user+"#"+ftp+"/?password="+password+"&recursive=true&passiveMode=true&streamDownload=true&fileName=${body}&delete="+borrado+"")
console log:
INFO | Apache Camel 2.15.1.redhat-621084 (CamelContext: camel-1) is
starting 0 [main] INFO org.apache.camel.impl.DefaultCamelContext -
Apache Camel 2.15.1.redhat-621084 (CamelContext: camel-1) is starting
INFO | JMX is enabled 10 [main] INFO
org.apache.camel.management.ManagedManagementStrategy - JMX is
enabled INFO | Loaded 185 type converters 208 [main] INFO
org.apache.camel.impl.converter.DefaultTypeConverter - Loaded 185
type converters INFO | AllowUseOriginalMessage is enabled. If access
to the original message is not needed, then its recommended to turn
this option off as it may improve performance. 395 [main] INFO
org.apache.camel.impl.DefaultCamelContext - AllowUseOriginalMessage
is enabled. If access to the original message is not needed, then its
recommended to turn this option off as it may improve performance.
INFO | StreamCaching is not in use. If using streams then its
recommended to enable stream caching. See more details at
http://camel.apache.org/stream-caching.html 395 [main] INFO
org.apache.camel.impl.DefaultCamelContext - StreamCaching is not in
use. If using streams then its recommended to enable stream caching.
See more details at http://camel.apache.org/stream-caching.html INFO
| Endpoint is configured with noop=true so forcing endpoint to be
idempotent as well 395 [main] INFO
org.apache.camel.component.file.FileEndpoint - Endpoint is configured
with noop=true so forcing endpoint to be idempotent as well INFO |
Using default memory based idempotent repository with cache max size:
1000 395 [main] INFO org.apache.camel.component.file.FileEndpoint -
Using default memory based idempotent repository with cache max size:
1000 INFO | Route: route1 started and consuming from:
Endpoint[file://./?fileName=Datos.xml&noop=true] 502 [main] INFO
org.apache.camel.impl.DefaultCamelContext - Route: route1 started and
consuming from: Endpoint[file://./?fileName=Datos.xml&noop=true] INFO
| Route: route2 started and consuming from: Endpoint[direct://ftp] 504
[main] INFO org.apache.camel.impl.DefaultCamelContext - Route: route2
started and consuming from: Endpoint[direct://ftp] INFO | Total 2
routes, of which 2 is started. 504 [main] INFO
org.apache.camel.impl.DefaultCamelContext - Total 2 routes, of which
2 is started. INFO | Apache Camel 2.15.1.redhat-621084 (CamelContext:
camel-1) started in 0.504 seconds 507 [main] INFO
org.apache.camel.impl.DefaultCamelContext - Apache Camel
2.15.1.redhat-621084 (CamelContext: camel-1) started in 0.504 seconds INFO | Created default XPathFactory
com.sun.org.apache.xpath.internal.jaxp.XPathFactoryImpl#5434283f 1533
[Camel (camel-1) thread #0 - file://./] INFO
org.apache.camel.builder.xml.XPathBuilder - Created default
XPathFactory
com.sun.org.apache.xpath.internal.jaxp.XPathFactoryImpl#5434283f INFO
| imagen: ftp://190.0.56.190:8021/pruebasumman/conductor/71708375.jpg
1635 [Camel (camel-1) thread #0 - file://./] INFO route1 - imagen:
ftp://190.0.56.190:8021/pruebasumman/conductor/71708375.jpg INFO |
Apache Camel 2.15.1.redhat-621084 (CamelContext: camel-1) is shutting
down 10521 [main] INFO org.apache.camel.impl.DefaultCamelContext -
Apache Camel 2.15.1.redhat-621084 (CamelContext: camel-1) is shutting
down INFO | Starting to graceful shutdown 2 routes (timeout 300
seconds) 10524 [main] INFO
org.apache.camel.impl.DefaultShutdownStrategy - Starting to graceful
shutdown 2 routes (timeout 300 seconds) INFO | Waiting as there are
still 3 inflight and pending exchanges to complete, timeout in 300
seconds. 10524 [Camel (camel-1) thread #2 - ShutdownTask] INFO
org.apache.camel.impl.DefaultShutdownStrategy - Waiting as there are
still 3 inflight and pending exchanges to complete, timeout in 300
seconds. INFO | Waiting as there are still 3 inflight and pending
exchanges to complete, timeout in 299 seconds. 11525 [Camel (camel-1)
thread #2 - ShutdownTask] INFO
org.apache.camel.impl.DefaultShutdownStrategy - Waiting as there are
still 3 inflight and pending exchanges to complete, timeout in 299
seconds. INFO | Waiting as there are still 3 inflight and pending
exchanges to complete, timeout in 298 seconds. 12528 [Camel (camel-1)
thread #2 - ShutdownTask] INFO
org.apache.camel.impl.DefaultShutdownStrategy - Waiting as there are
still 3 inflight and pending exchanges to complete, timeout in 298
seconds. INFO | Waiting as there are still 3 inflight and pending
exchanges to complete, timeout in 297 seconds. 13529 [Camel (camel-1)
thread #2 - ShutdownTask] INFO
org.apache.camel.impl.DefaultShutdownStrategy - Waiting as there are
still 3 inflight and pending exchanges to complete, timeout in 297
seconds. INFO | Waiting as there are still 3 inflight and pending
exchanges to complete, timeout in 296 seconds. 14540 [Camel (camel-1)
thread #2 - ShutdownTask] INFO
org.apache.camel.impl.DefaultShutdownStrategy - Waiting as there are
still 3 inflight and pending exchanges to complete, timeout in 296
seconds. INFO | Waiting as there are still 3 inflight and pending
exchanges to complete, timeout in 295 seconds. 15555 [Camel (camel-1)
thread #2 - ShutdownTask] INFO
org.apache.camel.impl.DefaultShutdownStrategy - Waiting as there are
still 3 inflight and pending exchanges to complete, timeout in 295
seconds. INFO | Waiting as there are still 3 inflight and pending
exchanges to complete, timeout in 294 seconds. 16568 [Camel (camel-1)
thread #2 - ShutdownTask] INFO
org.apache.camel.impl.DefaultShutdownStrategy - Waiting as there are
still 3 inflight and pending exchanges to complete, timeout in 294
seconds. INFO | Waiting as there are still 3 inflight and pending
exchanges to complete, timeout in 293 seconds. 17569 [Camel (camel-1)
thread #2 - ShutdownTask] INFO
org.apache.camel.impl.DefaultShutdownStrategy - Waiting as there are
still 3 inflight and pending exchanges to complete, timeout in 293
seconds. INFO | Waiting as there are still 3 inflight and pending
exchanges to complete, timeout in 292 seconds. 18574 [Camel (camel-1)
thread #2 - ShutdownTask] INFO
org.apache.camel.impl.DefaultShutdownStrategy - Waiting as there are
still 3 inflight and pending exchanges to complete, timeout in 292
seconds.
Thanks in advance.
Download image file in binary mode
By default, Camel FTP is downloading file by ASCII mode.
Add binary=true into your ftp route will turn from ASCII mode to binary mode

Nagios is active on CLI but not running on Web Interface

Good morning,
I have a problem with my Nagios configuration. This is the response of service nagios status :
root#SRV-SUPERVISION-BT:~# service nagios status
● nagios.service - LSB: Starts and stops the Nagios monitoring server
Loaded: loaded (/etc/init.d/nagios)
Active: active (running) since ven. 2016-06-17 09:47:46 CEST; 41min ago
Process: 458 ExecStart=/etc/init.d/nagios start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/nagios.service
├─533 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios...
├─553 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/...
├─555 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/...
├─556 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/...
├─558 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/...
├─559 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/...
├─560 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/...
└─623 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios...
juin 17 09:47:46 SRV-SUPERVISION-BT nagios[533]: nerd: Channel opathchecks r...y
juin 17 09:47:46 SRV-SUPERVISION-BT nagios[533]: nerd: Fully initialized and...!
juin 17 09:47:46 SRV-SUPERVISION-BT nagios[533]: wproc: Successfully registe...r
juin 17 09:47:46 SRV-SUPERVISION-BT nagios[533]: wproc: Registry request: na...3
juin 17 09:47:46 SRV-SUPERVISION-BT nagios[533]: wproc: Registry request: na...8
juin 17 09:47:46 SRV-SUPERVISION-BT nagios[533]: wproc: Registry request: na...9
juin 17 09:47:46 SRV-SUPERVISION-BT nagios[533]: wproc: Registry request: na...6
juin 17 09:47:46 SRV-SUPERVISION-BT nagios[533]: wproc: Registry request: na...0
juin 17 09:47:46 SRV-SUPERVISION-BT nagios[533]: wproc: Registry request: na...5
juin 17 09:47:48 SRV-SUPERVISION-BT nagios[533]: Successfully launched comma...3
Hint: Some lines were ellipsized, use -l to show in full.
But when I'm going on the web interface, Nagios Core is not running.
The configtest command is also right :
root#SRV-SUPERVISION-BT:~# service nagios configtest
Nagios Core 4.1.1
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 08-19-2015
License: GPL
Website: https://www.nagios.org
Reading configuration data...
Read main config file okay...
Read object config files okay...
Running pre-flight check on configuration data...
Checking objects...
Checked 8 services.
Checked 1 hosts.
Checked 1 host groups.
Checked 0 service groups.
Checked 1 contacts.
Checked 1 contact groups.
Checked 24 commands.
Checked 5 time periods.
Checked 0 host escalations.
Checked 0 service escalations.
Checking for circular paths...
Checked 1 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 5 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...
Total Warnings: 0
Total Errors: 0
Things look okay - No serious problems were detected during the pre-flight check
Object precache file created:
/usr/local/nagios/var/objects.precache
Also, this is the right of my /usr/local/nagios/var:
root#SRV-SUPERVISION-BT:/usr/local/nagios/bin# ls /usr/local/nagios/var -l
total 88
drwxrwsr-x 2 nagios nagios 4096 juin 16 23:59 archives
-rw-r--r-- 1 nagios nagios 34 juin 17 11:00 nagios.configtest
-rw-r--r-- 1 nagios nagios 4 juin 17 09:47 nagios.lock
-rw-r--r-- 1 nagios nagios 3007 juin 17 10:47 nagios.log
-rw-r--r-- 1 nagios nagios 12665 juin 17 09:47 objects.cache
-rw-r--r-- 1 nagios nagios 12665 juin 17 11:00 objects.precache
-rw------- 1 nagios nagios 13062 juin 17 10:47 retention.dat
drwxrwsr-x 2 nagios nagcmd 4096 juin 17 09:47 rw
drwxr-sr-x 3 root nagios 4096 juin 3 08:28 spool
-rw-rw-r-- 1 nagios nagios 13485 juin 17 11:26 status.dat
I'm on Debian :
root#SRV-SUPERVISION-BT:~# uname -a
Linux SRV-SUPERVISION-BT 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux
I do not understand the problem. If anyone can help me, thanks in advance.
First you must install fcgiwrap:
Depending on your distribution you should use your package manager.
Then, you should enable cgi module in your Web Server, for examle, in apache:
Finally, restart apache and it´s should be work.
You must install/run fcgiwrap and use it in your web-server apache/nginx/..

Resources