This is the Error :--
[stderr] AAPT2 aapt2-4.0.0-6051327-linux Daemon #7: Idle daemon unexpectedly exit. This should not happen.
Sat, 27 Feb 2021 18:14:51 GMT
[stderr] AAPT2 aapt2-4.0.0-6051327-linux Daemon #6: Idle daemon unexpectedly exit. This should not happen.
Sat, 27 Feb 2021 18:14:51 GMT
[stderr] AAPT2 aapt2-4.0.0-6051327-linux Daemon #5: Idle daemon unexpectedly exit. This should not happen.
Sat, 27 Feb 2021 18:14:51 GMT
[stderr] AAPT2 aapt2-4.0.0-6051327-linux Daemon #4: Idle daemon unexpectedly exit. This should not happen.
Sat, 27 Feb 2021 18:14:52 GMT
[stderr] AAPT2 aapt2-4.0.0-6051327-linux Daemon #1: Idle daemon unexpectedly exit. This should not happen.
Sat, 27 Feb 2021 18:14:52 GMT
[stderr] AAPT2 aapt2-4.0.0-6051327-linux Daemon #2: Idle daemon unexpectedly exit. This should not happen.
Sat, 27 Feb 2021 18:14:53 GMT
[stderr] AAPT2 aapt2-4.0.0-6051327-linux Daemon #3: Idle daemon unexpectedly exit. This should not happen.
Sat, 27 Feb 2021 18:14:53 GMT
[stderr] AAPT2 aapt2-4.0.0-6051327-linux Daemon #0: Idle daemon unexpectedly exit. This should not happen.
Sat, 27 Feb 2021 18:14:53 GMT
Error: ./gradlew exited with signal: SIGKILL
at ChildProcess.completionListener (/app/turtle/node_modules/#expo/xdl/node_modules/#expo/spawn-async/build/spawnAsync.js:51:23)
at Object.onceWrapper (events.js:418:26)
at ChildProcess.emit (events.js:311:20)
at ChildProcess.EventEmitter.emit (domain.js:482:12)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
...
at spawnAsync (/app/turtle/node_modules/#expo/xdl/node_modules/#expo/spawn-async/build/spawnAsync.js:17:21)
at spawnAsyncThrowError (/app/turtle/node_modules/#expo/xdl/build/detach/ExponentTools.js:201:45)
at buildShellAppAsync (/app/turtle/node_modules/#expo/xdl/build/detach/AndroidShellApp.js:976:11)
at async Object.createAndroidShellAppAsync (/app/turtle/node_modules/#expo/xdl/build/detach/AndroidShellApp.js:396:5)
at async runShellAppBuilder (/app/turtle/build/builders/android.js:95:9)
at async Object.buildAndroid [as android] (/app/turtle/build/builders/android.js:43:28)
at async build (/app/turtle/build/jobManager.js:181:33)
at async processJob (/app/turtle/build/jobManager.js:118:32)
at async Object.doJob (/app/turtle/build/jobManager.js:49:5)
at async main (/app/turtle/build/server.js:66:13)
This error is with Expo React Native.
Everything was working fine until I ran the command expo build:android
Here is the URL to all of the Logs
Abhyuday Tripathi
In my case I just closed and re-open the terminal and ran below command:
expo build:android -t apk
Do nothing, just try again. It is not your problem.
I ran into a very similar error after updating my global Expo npm package.
For some reason, an app that would always build crashed during building with that error.
As I hadn't done any changes to the actual app, I deleted the app/project from
expo.io, and rebuilt it with the expo build command. This made the build succeed.
I'm just leaving this here as an answer, in case someone runs into the same error after updating Expo.
First time I had this problem, reason was I've used an invalid slug name in app.json, there must be a dash between the words as below :
"expo": {
"slug": "My-App",
After a while I had the same problem,
I've realized that my expo-cli version wasn't latest one, I've
updated it
Just closed and re-opened the VS Code and terminal as
Zain said above in this page
Related
I uninstalled apache, php, mysql, proftpd, wordpress, cerbot and letsencrypt to get a new, fresh install of apache.
After uninstalling all packages and reinstalling apache, i got this error:
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.
invoke-rc.d: initscript apache2, action "restart" failed.
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2021-08-28 15:46:46 CEST; 23ms ago
Docs: https://httpd.apache.org/docs/2.4/
Process: 10693 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
Aug 28 15:46:46 raspberrypi systemd[1]: Starting The Apache HTTP Server...
Aug 28 15:46:46 raspberrypi apachectl[10693]: apache2: Syntax error on line 225 of /etc/apache2/apache2.conf: Syntax error on line 33 of /etc/apache2/sites-enabled/000-default-le-ssl.conf: Could not open configuration file /etc/letsencrypt/options-ssl-apache.conf: No such file or directory
Aug 28 15:46:46 raspberrypi apachectl[10693]: Action 'start' failed.
Aug 28 15:46:46 raspberrypi apachectl[10693]: The Apache error log may have more information.
Aug 28 15:46:46 raspberrypi systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
Aug 28 15:46:46 raspberrypi systemd[1]: apache2.service: Failed with result 'exit-code'.
Aug 28 15:46:46 raspberrypi systemd[1]: Failed to start The Apache HTTP Server.
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for systemd (241-7~deb10u8+rpi1) ...
I tried to remove all apache-related packages by
sudo apt-get remove apache2
sudo apt autoremove
but this didn't work either.
You have an typing error on line 225 of file /etc/apache2/apache2.conf
I flashed a new image onto the Pi because I couldn't make it run.
When I check status of libvirtd using the cmd: sudo systemctl status libvirtd the o/p is as follows:
● libvirtd.service - Virtualization daemon
Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Thu 2021-07-22 18:00:59 EDT; 1min 4s ago
TriggeredBy: ● libvirtd-admin.socket
● libvirtd.socket
● libvirtd-ro.socket
Docs: man:libvirtd(8)
https://libvirt.org
Process: 1717 ExecStart=/usr/sbin/libvirtd $libvirtd_opts (code=exited, status=0/SUCCESS)
Main PID: 1717 (code=exited, status=0/SUCCESS)
Jul 22 18:00:59 eb2-2259-lin04 systemd[1]: Starting Virtualization daemon...
Jul 22 18:00:59 eb2-2259-lin04 systemd[1]: Started Virtualization daemon.
Jul 22 18:00:59 eb2-2259-lin04 libvirtd[1717]: libvirt version: 6.0.0, package: 0ubuntu8.11 (Christian Ehrhardt <christian.ehrhardt#canonical.com> Tue, 05 Jan 2021 13:48:48 +0100)
Jul 22 18:00:59 libvirtd[1717]: hostname: eb2-2259-lin04
Jul 22 18:00:59 eb2-2259-lin04 libvirtd[1717]: invalid argument: Failed to parse user 'libvirt-qemu'
Jul 22 18:00:59 eb2-2259-lin04 libvirtd[1717]: Initialization of QEMU state driver failed: invalid argument: Failed to parse user 'libvirt-qemu'
Jul 22 18:00:59 eb2-2259-lin04 libvirtd[1717]: Driver state initialization failed
Jul 22 18:00:59 eb2-2259-lin04 systemd[1]: libvirtd.service: Succeeded.
The status is always inactive(dead). And I get lines invalid argument: Failed to parse user 'libvirt-qemu' , Initialization of QEMU state driver failed: invalid argument: Failed to parse user 'libvirt-qemu' and Driver state initialization failed
I also tried sudo systemctl start libvirtd
and sudo systemctl status libvirtd but the issue doesn't get resolved.
I was actually installing KVM2 driver for GPU support within minikube following the link [https://help.ubuntu.com/community/KVM/Installation][1]. According to the link KVM2 is successfully installed in Ubuntu if virsh list --all cmd does not return an error. For me all the steps returned no error except for the virsh list --all returned the following error.
error: failed to connect to the hypervisor
error: Cannot recv data: Connection reset by peer
and sometimes returns the following error
error: failed to connect to the hypervisor
error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Connection refused
When I start minikube with kvm2 as the driver using the command minikube start --driver kvm2I get the following error
😄 minikube v1.15.1 on Ubuntu 20.04
💢 Exiting due to GUEST_DRIVER_MISMATCH: The existing "minikube" cluster was created using the "virtualbox" driver, which is incompatible with requested "kvm2" driver.
💡 Suggestion: Delete the existing 'minikube' cluster using: 'minikube delete', or start the existing 'minikube' cluster using: 'minikube start --driver=virtualbox'
Please suggest me how to start minikube with kvm2 as driver.
I have a problem with apache2 start.
When I try apache start i have the message:
root#ocsi:/var/log/apache2# **systemctl start apache2.service**
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.
in systemctl status apache2.service
root#ocsi:/var/log/apache2# systemctl status apache2.service
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2020-06-01 07:53:07 CEST; 19s ago
Docs: https://httpd.apache.org/docs/2.4/
Process: 3142 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
Jun 01 07:53:07 ocsi systemd[1]: Starting The Apache HTTP Server...
Jun 01 07:53:07 ocsi apachectl[3142]: Action 'start' failed.
Jun 01 07:53:07 ocsi apachectl[3142]: The Apache error log may have more information.
Jun 01 07:53:07 ocsi systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
Jun 01 07:53:07 ocsi systemd[1]: apache2.service: Failed with result 'exit-code'.
Jun 01 07:53:07 ocsi systemd[1]: Failed to start The Apache HTTP Server.
in journalctl -xe
root#ocsi:/var/log/apache2# journalctl -xe
Jun 01 07:54:31 ocsi multipathd[700]: sda: add missing path
Jun 01 07:54:31 ocsi multipathd[700]: sda: failed to get udev uid: Invalid argument
Jun 01 07:54:31 ocsi multipathd[700]: sda: failed to get sysfs uid: Invalid argument
Jun 01 07:54:31 ocsi multipathd[700]: sda: failed to get sgio uid: No such file or directory
and in apache2 log is:
root#ocsi:/var/log/apache2# vi error.log
[Mon Jun 01 07:53:07.305344 2020] [perl:error] [pid 3149] Can't locate SOAP/Transport/HTTP.pm in #INC (you may need to install the SOAP::Transport::HTTP module) (#INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /etc/apache2) at /usr/local/share/perl/5.30.0/Apache/Ocsinventory/Plugins/Apache.pm line 25.\nBEGIN failed--compilation aborted at /usr/local/share/perl/5.30.0/Apache/Ocsinventory/Plugins/Apache.pm line 25.\nCompilation failed in require at (eval 16) line 1.\n
[Mon Jun 01 07:53:07.305621 2020] [perl:error] [pid 3149] Can't load Perl module Apache::Ocsinventory::Plugins::Apache for server localhost:0, exiting...
My system:
PHP Version : 7.4.3
Server version: Apache/2.4.41 (Ubuntu)
Description: Ubuntu 20.04 LTS
Ubuntu Linux 5.4.0-33-generic x86_64
How can I fix this error?
Looks like you need to install the SOAP::Lite module. That can be done by running:
$ sudo apt-get install libsoap-lite-perl
For more details, read on.
The error message is telling you that the Perl compiler can't find the module SOAP::Transport::HTTP (which is presumably used in some code used in your Apache start-up).
This module has never been part of a standard Perl distribution (you can test that by running corelist SOAP::Transport::HTTP). It, therefore, needs to be installed separately.
Perl modules are usually installed from CPAN. If you search for the module there, you'll see it's part of the SOAP-Lite distribution. Now you could install it directly from there using cpan but, given in this case, the easier approach is probably to install the pre-built package for your operating system. And that's done by running the command above.
I am trying to implement a python module (say, my-module) on arm32v7 Raspberry Pi-3 model. The module is based on resin/rpi-raspbian:stretch (azure-iothub-device-client==1.4.0b0). I have the iothub_client python library then working fine inside the module.
However when I am trying to deploy and do the iotedgectl start in the Pi, I get the following error in docker logs -f <my-module> :
Python 2.7.13 (default, Nov 24 2017, 17:33:09)
[GCC 6.3.0 20170516]
IoT Hub Client for Python
Adding TrustedCerts from: /mnt/edgemodule/edge-device-ca.cert.pem
set_option TrustedCerts successful
Converted audio file 2643035.wav in 5.67014288902 seconds
Payload: {"translatedutctime": "2018-06-23T14:56:59.972036", "filename": "2643035.wav"}
Sending Payload for 2643035.wav ...
Error: Time:Sat Jun 23 14:56:59 2018 File:/usr/sdk/src/c/c-utility/adapters/socketio_berkeley.c Func:socketio_open Line:701 Failure: connect failure 111.
Error: Time:Sat Jun 23 14:56:59 2018 File:/usr/sdk/src/c/c-utility/src/tlsio_openssl.c Func:on_underlying_io_open_complete Line:751 Invalid tlsio_state. Expected state is TLSIO_STATE_OPENING_UNDERLYING_IO.
Error: Time:Sat Jun 23 14:56:59 2018 File:/usr/sdk/src/c/c-utility/src/tlsio_openssl.c Func:tlsio_openssl_open Line:1251 Failed opening the underlying I/O.
Error: Time:Sat Jun 23 14:56:59 2018 File:/usr/sdk/src/c/umqtt/src/mqtt_client.c Func:mqtt_client_connect Line:980 Error: io_open failed
Error: Time:Sat Jun 23 14:56:59 2018 File:/usr/sdk/src/c/iothub_client/src/iothubtransport_mqtt_common.c Func:SendMqttConnectMsg Line:1932 failure connecting to address elderberrypi.
Error: Time:Sat Jun 23 14:57:00 2018 File:/usr/sdk/src/c/c-utility/adapters/socketio_berkeley.c Func:socketio_open Line:701 Failure: connect failure 111.
Error: Time:Sat Jun 23 14:57:00 2018 File:/usr/sdk/src/c/c-utility/src/tlsio_openssl.c Func:on_underlying_io_open_complete Line:751 Invalid tlsio_state. Expected state is TLSIO_STATE_OPENING_UNDERLYING_IO.
Error: Time:Sat Jun 23 14:57:00 2018 File:/usr/sdk/src/c/c-utility/src/tlsio_openssl.c Func:tlsio_openssl_open Line:1251 Failed opening the underlying I/O.
Error: Time:Sat Jun 23 14:57:00 2018 File:/usr/sdk/src/c/umqtt/src/mqtt_client.c Func:mqtt_client_connect Line:980 Error: io_open failed
Error: Time:Sat Jun 23 14:57:00 2018 File:/usr/sdk/src/c/iothub_client/src/iothubtransport_mqtt_common.c Func:SendMqttConnectMsg Line:1932 failure connecting to address elderberrypi.
Error: Time:Sat Jun 23 14:57:02 2018 File:/usr/sdk/src/c/c-utility/adapters/socketio_berkeley.c Func:socketio_open Line:701 Failure: connect failure 111.
Error: Time:Sat Jun 23 14:57:02 2018 File:/usr/sdk/src/c/c-utility/src/tlsio_openssl.c Func:on_underlying_io_open_complete Line:751 Invalid tlsio_state. Expected state is TLSIO_STATE_OPENING_UNDERLYING_IO.
Error: Time:Sat Jun 23 14:57:02 2018 File:/usr/sdk/src/c/c-utility/src/tlsio_openssl.c Func:tlsio_openssl_open Line:1251 Failed opening the underlying I/O.
Error: Time:Sat Jun 23 14:57:02 2018 File:/usr/sdk/src/c/umqtt/src/mqtt_client.c Func:mqtt_client_connect Line:980 Error: io_open failed
Error: Time:Sat Jun 23 14:57:02 2018 File:/usr/sdk/src/c/iothub_client/src/iothubtransport_mqtt_common.c Func:SendMqttConnectMsg Line:1932 failure connecting to address elderberrypi.
Converted audio file 4417734.wav in 4.16613197327 seconds
Payload: {"translatedutctime": "2018-06-23T14:57:04.059473", "filename": "4417734.wav"}
Sending Payload for 4417734.wav ...
Error: Time:Sat Jun 23 14:57:06 2018 File:/usr/sdk/src/c/c-utility/adapters/socketio_berkeley.c Func:socketio_open Line:701 Failure: connect failure 111.
Error: Time:Sat Jun 23 14:57:06 2018 File:/usr/sdk/src/c/c-utility/src/tlsio_openssl.c Func:on_underlying_io_open_complete Line:751 Invalid tlsio_state. Expected state is TLSIO_STATE_OPENING_UNDERLYING_IO.
Error: Time:Sat Jun 23 14:57:06 2018 File:/usr/sdk/src/c/c-utility/src/tlsio_openssl.c Func:tlsio_openssl_open Line:1251 Failed opening the underlying I/O.
Error: Time:Sat Jun 23 14:57:06 2018 File:/usr/sdk/src/c/umqtt/src/mqtt_client.c Func:mqtt_client_connect Line:980 Error: io_open failed
Error: Time:Sat Jun 23 14:57:06 2018 File:/usr/sdk/src/c/iothub_client/src/iothubtransport_mqtt_common.c Func:SendMqttConnectMsg Line:1932 failure connecting to address elderberrypi.
Converted audio file 4486452.wav in 4.94396114349 seconds
Payload: {"translatedutctime": "2018-06-23T15:32:28.491401", "filename": "4486452.wav"}
Sending Payload for 4486452.wav ...
Confirmation[0] received for message with result = MESSAGE_TIMEOUT
Properties: {}
Total calls confirmed: 1
Now this goes on for several messages, and only after the start (never in between, once it stabilizes). After several such message timeouts and errors, the scenario returns back to normal, with callback confirmation, and I am also, able to receive the messages in IoTHub. As a result I always miss the first 5-10 messages and am unable to see those messages in IotHub.
After much trouble shooting, I figured there is a consistent problem. The edgeHub module always seems to fully initialize several seconds after my-module already start sending messages. Since edgeHub is not fully initialized and TLS authentication and MQTT paths are not set, the first few messages of my-module are lost. Maybe this is because the raspberry pi is a slow device?
I have tried starting my-module manually, after the edgeHub is fully initialized, all messages are delivered without any issues in that case.
Question: Is there a way to wait for the edgeHub to fully initialize and then start sending messages? More importantly, is this the actual problem or something else altogether is the cause of the issue?
Please let me know if more information is needed to get the problem context. I have tried to keep my query concise :)
What you pointed out is an accurate description of current behavior! As of current implementation, all modules are started at the same time. Some of them are initialized faster than edgeHub, which caused the behavior you'd seen. This is a known problem and we are implementing a fix!
This was working just Friday. No change in code. (Other than doing a time machine backup in Mac).
But since today react-native run-ios just does not seem to be working. The simulator comes up, but then the usual loading http://localhost:8081 does not show up any more. No errors or any indication on why this is failing. The simulator shows my App in home screen. Double clicking it just brings up and the app seems to crash immediately.
But react-native run-android works fine.
Am not sure where to even begin debugging this. (Am new to whole app development).
A few observations,
when I run npm start and then run react-native run-ios, it
usually "detects" that packager is running and skips launchPackager command, but today its not the case, the launchPackager opens regardless of whether a package is already running (Happens both with run-android and run-ios
There is usually below lines once the app begins loading. But today they only show up when I run react-native run-android
8:43:46 PM] find dependencies
transformed 728/728 (100%)
[8:43:46 PM] find dependencies (553ms)
[8:43:46 PM] request:/index.android.bundle?platform=android&dev=true&hot=false&minify=false (661ms)
And when I run react-native logs-ios, I get the below errors
Sep 12 20:53:15 sseshac-in-la com.apple.CoreSimulator.SimDevice.ADE00521-C04E-4EC5-8BE2-FE729523A0B9.launchd_sim[3812] (UIKitApplication:org.reactjs.native.example.X[0x3f02][4589]) <Notice>: Service exited due to signal: Abort trap: 6
Sep 12 20:53:15 sseshac-in-la assertiond[3832] <Error>: assertion failed: 15G31 13E230: assertiond + 15801 [3C808658-78EC-3950-A264-79A64E0E463B]: 0x1
Sep 12 20:53:15 sseshac-in-la Unknown[3832] <Error>:
Sep 12 20:53:15 sseshac-in-la SpringBoard[3828] <Warning>: Application 'UIKitApplication:org.reactjs.native.example.X[0x3f02]' crashed.
Sep 12 20:53:15 sseshac-in-la assertiond[3832] <Error>: assertion failed: 15G31 13E230: assertiond + 15801 [3C808658-78EC-3950-A264-79A64E0E463B]: 0x1
Sep 12 20:53:15 sseshac-in-la Unknown[3832] <Error>:
Sep 12 20:53:15 sseshac-in-la assertiond[3832] <Warning>: notify_suspend_pid() failed with error 7
Sep 12 20:53:15 sseshac-in-la assertiond[3832] <Error>: assertion failed: 15G31 13E230: assertiond + 15801 [3C808658-78EC-3950-A264-79A64E0E463B]: 0x1
Sep 12 20:53:15 sseshac-in-la Unknown[3832] <Error>:
Sep 12 20:53:15 sseshac-in-la SpringBoard[3828] <Warning>: Reply Error: Connection interrupted
Sep 12 20:58:36 sseshac-in-la routined[3817] <Error>: CoreLocation: Error occurred while trying to retrieve motion state update: CMErrorDomain Code:104
UPDATE:
I think the root cause seems to below error
<Error>: *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'bundleURL must be non-nil when not implementing loadSourceForBridge'
Note that I am using React native 0.32. I understood that now it "detects" rather than hardcoding the bundleUrl. If someone can throw light on where this "detection" is, will be helpful
Problem turned out to be I was missing an entry in /etc/hosts
127.0.0.1 localhost
I still don't have any clue why it would work before. But that solved it
Probably you have problem with the packager make sure your modules all built you can check by opening
http://localhost:8081/index.ios.bundle?platform=ios&dev=true
in the browser after the build you will get the error