Starting today the uploat artifact part of out Action is failing with this:
Container for artifact "shuttle_23.1.19.293.zip" successfully created. Starting upload of file(s)
Total file count: 1 ---- Processed file #0 (0.0%)
Total file count: 1 ---- Processed file #0 (0.0%)
Total file count: 1 ---- Processed file #0 (0.0%)
Total file count: 1 ---- Processed file #0 (0.0%)
An error has been caught http-client index 0, retrying the upload
Error: write ECONNRESET
at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:98:16) {
errno: -4077,
code: 'ECONNRESET',
syscall: 'write'
}
Exponential backoff for retry #1. Waiting for 6623 milliseconds before continuing the upload at offset 0
Finished backoff for retry #1, continuing with upload
No idea what this means. And is sometimes DOES work, but mostly does not.
Anyone else ever see this? I expect upload-artifact#v3 is a pretty common action.
Related
While running the JMeter for data driven testing, JMeter is thrown with the error below. A big chunk of data was not pulled in. CSV file has about 1500 email ids and would like to ramp up the test to a million. However, the test is failing at the first attempt itself.
Any thoughts, please. Appreciate your help.
2019-03-19 23:55:08,169 ERROR o.a.j.c.CSVDataSet: java.io.IOException: File never reserved: C:\Users\sp\Desktop\STM\STM-JMeterTests\emailAdd.csv
2019-03-19 23:55:08,572 INFO o.a.j.t.JMeterThread: Thread is done: emailAdd 1-5
2019-03-19 23:55:08,572 INFO o.a.j.t.JMeterThread: Thread finished: emailAdd 1-5
2019-03-19 23:55:08,594 ERROR o.a.j.c.CSVDataSet: java.io.IOException: File never reserved: C:\Users\sp\Desktop\STM\STM-JMeterTests\emailAdd.csv
2019-03-19 23:55:08,595 ERROR o.a.j.c.CSVDataSet: java.io.IOException: File never reserved: C:\Users\sp\Desktop\STM\STM-JMeterTests\emailAdd.csv
2019-03-19 23:55:08,607 INFO o.a.j.t.JMeterThread: Thread is done: emailAdd 1-4
A week ago he compiled without problems and could test my project via web, but these days I've been testing and fault me:
The error is as follows:
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':html:superDev'.
Process ' command '/usr/lib/jvm/java-7-openjdk-amd64/bin/java' ' finished with non-zero exit value 1
BUILD FAILED
I am following the chapter 1 of tutorial http://gettingstartedwithchef.com/ and downloaded all dependencies listed in chapter1. The command "chef-solo -c solo.rb -j web.json" should be working, but I got the following error.
I googled the error that is shown as below and found that someone suggested to run a resource before any others (like to configure a package manager, apt/yum/etc). But how to do this? All links redirected to chef homepage...
Any suggestion would be appreciated.
yum_package[mysql] action install
* No candidate version available for mysql
================================================================================
Error executing action `install` on resource 'yum_package[mysql]'
================================================================================
Chef::Exceptions::Package
-------------------------
No candidate version available for mysql
Resource Declaration:
---------------------
# In /root/chef-repo/cookbooks/mysql/recipes/client.rb
47: package name
48: end
Compiled Resource:
------------------
# Declared in /root/chef-repo/cookbooks/mysql/recipes/client.rb:47:in `block in from_file'
yum_package("mysql") do
action :install
retries 0
retry_delay 2
default_guard_interpreter :default
package_name "mysql"
timeout 900
flush_cache {:before=>false, :after=>false}
declared_type :package
cookbook_name :mysql
recipe_name "client"
end
Running handlers:
[2015-05-15T10:28:13-04:00] ERROR: Running exception handlers
Running handlers complete
[2015-05-15T10:28:13-04:00] ERROR: Exception handlers complete
[2015-05-15T10:28:13-04:00] FATAL: Stacktrace dumped to /root/chef-solo/chef-stacktrace.out
Chef Client failed. 0 resources updated in 4.248307605 seconds
[2015-05-15T10:28:13-04:00] ERROR: yum_package[mysql] (mysql::client line 47) had an error: Chef::Exceptions::Package: No candidate version available for mysql
[2015-05-15T10:28:13-04:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
MySQL is distributed via the 'mysql-server' and 'mysql-client' packages.
You can use one of those to satisfy your dependency.
yum_package("mysql-server") do
...
package_name "mysql-server"
or
yum_package("mysql-client") do
...
package_name "mysql-client"
Those packages are wrappers that (currently) point to 'mysql-server-5.6' and 'mysql-client-5.6' respectively. If you need a different version (for example: mysql-client-5.1), you can specify it instead.
yum_package("mysql-client-5.1") do
...
package_name "mysql-client-5.1"
I have set up MySQL NDB Cluster 7.3.5 and the cluster was working fine.
Cluster with 4 nodes :
NodeA : SQLNode1, DataNode1
NodeB : SQLNode2, DataNode2
NodeC : Mgmt Node1
NodeD : Mgmt Node2
To test the server reboot scenario I rebooted VMWare ESXi and restarted all VMs.
But the data nodes are subsequently failing to start.
Adding logs for the servers respectively:
/home/mysql/mysqlcluster_data/1/ndb_1_out.log (Data Node 1)
error: [ code: 708 line: 38848236 node: 1 count: 1 status: 32687 key: 445914048 name: 'hhmefep/def/fgvmev0000000000-elog-1398414831' ]
2014-05-13 13:16:40 [ndbd] INFO -- Failed to recreate object 505 during restart, error 708.
2014-05-13 13:16:40 [ndbd] INFO -- DBDICT (Line: 4688) 0x00000000
2014-05-13 13:16:40 [ndbd] INFO -- Error handler restarting system
2014-05-13 13:16:40 [ndbd] INFO -- Error handler shutdown completed - exiting
2014-05-13 13:16:40 [ndbd] ALERT -- Angel detected too many startup failures(3), not restarting again
2014-05-13 13:16:40 [ndbd] ALERT -- Node 1: Forced node shutdown completed. Occured during startphase 4. Caused by error 2355: 'Failure to restore schema(Resource configuration error). Permanent error, external action needed'.
It seems that the nodes are failing to recover this table:
hhmefep.fgvmev0000000000-elog-1398414831
/home/mysql/mysqlcluster_data/2/ndb_2_out.log (Data Node 2)
2014-05-13 13:05:48 [ndbd] INFO -- Start phase 1 completed
2014-05-13 13:05:48 [ndbd] INFO -- Start phase 2 completed
2014-05-13 13:05:48 [ndbd] INFO -- Start phase 3 completed
2014-05-13 13:05:51 [ndbd] INFO -- Node 1 disconnected
2014-05-13 13:05:51 [ndbd] INFO -- QMGR (Line: 3308) 0x00000000
2014-05-13 13:05:51 [ndbd] INFO -- Error handler restarting system
2014-05-13 13:05:51 [ndbd] INFO -- Error handler shutdown completed - exiting
2014-05-13 13:05:51 [ndbd] ALERT -- Angel detected too many startup failures(3), not restarting again
2014-05-13 13:05:51 [ndbd] ALERT -- Node 2: Forced node shutdown completed. Occured during startphase 4. Caused by error 2308: 'Another node failed during system restart, please investigate error(s) on other node(s)(Restart error). Temporary error, restart node'.
It seems that data node 2 is trying to sync with data node 1 but has been forcefully shutdown by management node.
(Mgmt Node)
ndb_mgm> Node 1: Forced node shutdown completed, restarting. Occured during startphase 4. Caused by error 2355: 'Failure to restore schema(Resource configuration error). Permanent error, external action needed'.
Node 1: Forced node shutdown completed, restarting. Occured during startphase 4. Caused by error 2355: 'Failure to restore schema(Resource configuration error). Permanent error, external action needed'.
Node 1: Forced node shutdown completed. Occured during startphase 4. Caused by error 2355: 'Failure to restore schema(Resource configuration error). Permanent error, external action needed'.
Node 2: Forced node shutdown completed, restarting. Occured during startphase 4. Caused by error 2308: 'Another node failed during system restart, please investigate error(s) on other node(s)(Restart error). Temporary error, restart node'.
Node 2: Forced node shutdown completed, restarting. Occured during startphase 4. Caused by error 2355: 'Failure to restore schema(Resource configuration error). Permanent error, external action needed'.
ndb_mgm> Node 2: Forced node shutdown completed. Occured during startphase 4. Caused by error 2355: 'Failure to restore schema(Resource configuration error). Permanent error, external action needed'.
Please help me on this since it is very frustrating.
Per the MySQL memory engine page:
The MEMORY storage engine (formerly known as HEAP) creates
special-purpose tables with contents that are stored in memory.
Because the data is vulnerable to crashes, hardware issues, or power
outages, only use these tables as temporary work areas or read-only
caches for data pulled from other tables.
Any clues why I would be getting the following error when trying my application with
apache/passenger/mysql while the same runs fine with webtrick?
[ 2013-05-12 01:39:31.3313 26429/7f0535e4b700 Pool2/Implementation.cpp:762 ]: Could not spawn process for group /home/ruby/work/depot#default: An error occurred while starting up the preloader: it did not write a handshake message in time.
in 'void Passenger::ApplicationPool2::SmartSpawner::throwPreloaderSpawnException(const std::string&, Passenger::SpawnException::ErrorKind, Passenger::ApplicationPool2::Spawner::BackgroundIOCapturerPtr&, const Passenger::ApplicationPool2::Spawner::DebugDirPtr&)' (SmartSpawner.h:149)
in 'std::string Passenger::ApplicationPool2::SmartSpawner::negotiatePreloaderStartup(Passenger::ApplicationPool2::SmartSpawner::StartupDetails&)' (SmartSpawner.h:539)
in 'void Passenger::ApplicationPool2::SmartSpawner::startPreloader()' (SmartSpawner.h:205)
in 'virtual Passenger::ApplicationPool2::ProcessPtr Passenger::ApplicationPool2::SmartSpawner::spawn(const Passenger::ApplicationPool2::Options&)' (SmartSpawner.h:743)
in 'void Passenger::ApplicationPool2::Group::spawnThreadRealMain(const Passenger::ApplicationPool2::SpawnerPtr&, const Passenger::ApplicationPool2::Options&, unsigned int)' (Implementation.cpp:695)
[ 2013-05-12 01:39:31.3315 26429/7f053688d700 agents/HelperAgent/RequestHandler.h:1884 ]: [Client 20] Cannot checkout session. An error occurred while starting up the preloader: it did not write a handshake message in time.
What helped in my case was removing access to /etc/profile - check if you don't have some blocking calls there or in bashrc/bash_profile etc. Passenger is spawning bash process to start the application and it's reading profile/rc. I know it's late answer but maybe it will help someone.