I am following the instructions here to install Telit asset gateway on my Raspberry Pi. This is a fresh install of 64-bit Pi OS running on a Pi 4.
Installation seems to go well and I get the message
Updating file permissions...
Running post-install commands...
systemd detected, installing deviceWISE services
Installation is complete.
I then check to see if the service is running using systemctl status devicewise.service and it returns this:
● devicewise.service - deviceWISE Asset Gateway
Loaded: loaded (/etc/systemd/system/devicewise.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-12-07 17:19:36 GMT; 19ms ago
Main PID: 2846
Tasks: 1 (limit: 4164)
CPU: 6ms
CGroup: /system.slice/devicewise.service
Dec 07 17:19:36 raspberrypi systemd[1]: Started deviceWISE Asset Gateway.
Dec 07 17:19:36 raspberrypi systemd[2846]: devicewise.service: Failed to execute /opt/dw/dwcore/dwcore: No such file or directory
Dec 07 17:19:36 raspberrypi systemd[2846]: devicewise.service: Failed at step EXEC spawning /opt/dw/dwcore/dwcore: No such file or di>
Dec 07 17:19:36 raspberrypi systemd[1]: devicewise.service: Main process exited, code=exited, status=203/EXEC
Dec 07 17:19:36 raspberrypi systemd[1]: devicewise.service: Failed with result 'exit-code'.
If I then try again it shows this:
● devicewise.service - deviceWISE Asset Gateway
Loaded: loaded (/etc/systemd/system/devicewise.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2022-12-07 17:19:55 GMT; 2s ago
Process: 2852 ExecStart=/opt/dw/dwcore/dwcore (code=exited, status=203/EXEC)
Main PID: 2852 (code=exited, status=203/EXEC)
CPU: 6ms
Telit requires the 32-bit version of Raspberry Pi OS to be running. Hopefully there will be a 64-bit version of DeviceWise for ARM in the near future.
I have problem when starting VNC it giving error looks like this :
Job for vncserver#:1.service failed because the control process exited with error code. See "systemctl status vncserver#:1.service" and "journalctl -xe" for details.
when i check the status the error looks like this :
vncserver#:1.service - Remote desktop service (VNC)
Loaded: loaded (/etc/systemd/system/vncserver#:1.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2021-05-07 07:43:11 UTC; 10s ago
Process: 2442 ExecStart=/usr/bin/vncserver %I (code=exited, status=2)
Process: 2436 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)
May 07 07:43:11 dev-srv-nlr systemd[1]: Starting Remote desktop service (VNC)...
May 07 07:43:11 dev-srv-nlr systemd[1]: vncserver#:1.service: control process exited, code=exited status=2
May 07 07:43:11 dev-srv-nlr systemd[1]: Failed to start Remote desktop service (VNC).
May 07 07:43:11 dev-srv-nlr systemd[1]: Unit vncserver#:1.service entered failed state.
May 07 07:43:11 dev-srv-nlr systemd[1]: vncserver#:1.service failed.
do you know how to solve this ? Thanks in advance.
After I installed couchdb， I could get the welcome information
$ curl localhost:5984
{"couchdb":"Welcome","version":"2.1.2","features":["scheduler"],"vendor":{"name":"The Apache Software Foundation"}}
But I can't check the status by systemctl
$ systemctl status couchdb.service
● couchdb.service
Loaded: not-found (Reason: No such file or directory)
Active: failed (Result: start-limit-hit) since 一 2018-12-03 14:52:14 CST; 6min ago
Main PID: 30946 (code=killed, signal=USR2)
12月 03 14:52:14 gpuhuawei systemd[1]: couchdb.service: Unit entered failed state.
12月 03 14:52:14 gpuhuawei systemd[1]: couchdb.service: Failed with result 'signal'.
12月 03 14:52:14 gpuhuawei systemd[1]: couchdb.service: Service hold-off time over, scheduling restart.
12月 03 14:52:14 gpuhuawei systemd[1]: Stopped Apache CouchDB.
12月 03 14:52:14 gpuhuawei systemd[1]: couchdb.service: Start request repeated too quickly.
12月 03 14:52:14 gpuhuawei systemd[1]: Failed to start Apache CouchDB.
12月 03 14:52:14 gpuhuawei systemd[1]: couchdb.service: Unit entered failed state.
12月 03 14:52:14 gpuhuawei systemd[1]: couchdb.service: Failed with result 'start-limit-hit'.
12月 03 14:53:53 gpuhuawei systemd[1]: Stopped Apache CouchDB.
12月 03 14:53:53 gpuhuawei systemd[1]: Stopped Apache CouchDB.
When I run couchdb by command line, I got
$ couchdb
{"init terminating in do_boot",{{badmatch,{error,{bad_return,{{couch_app,start,[normal,["/etc/couchdb/default.ini","/etc/couchdb/local.ini"]]},{'EXIT',{{badmatch,{error,{error,eacces}}},[{couch_server_sup,start_server,1,[{file,"couch_server_sup.erl"},{line,56}]},{application_master,start_it_old,4,[{file,"application_master.erl"},{line,273}]}]}}}}}},[{couch,start,0,[{file,"couch.erl"},{line,18}]},{init,start_it,1,[]},{init,start_em,1,[]}]}}
[1] 2288 user-defined signal 2 couchdb
My work enviroment
$ uname -a
Linux gpuhuawei 4.15.0-34-generic #37~16.04.1-Ubuntu SMP Tue Aug 28 10:44:06 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
This is a bit late, but the "start-limit-hit" message is a red herring. I have seen something very similar with a Moodle installation using MySQL and it's actually saying that you (or the service start process) have tried to restart the database too many times or too soon after a failed attempt to start. Basically, this start-limit-hit message is saying "stop trying to do the same thing and expecting different results".
The actual issue will be further up in the syslog. Unhelpfully, service status does not return enough lines of the error messages to actually see what is wrong. Try a service start, and go and look in the actual syslog, and you will see the series of start attempts and a line just above each one hopefully will tell you the actual issue. In my case here, you can see that the problem is the mount point containing the database is missing - thanks, Azure. For one attempt of service start, it tries to start 5 times in quick succession, failing each time because the data dir was not mounted, and on the sixth it fails with the start-limit-hit.
Always back up your data/ and etc/ directories prior to upgrading CouchDB.
We recommend that you overwrite your etc/default.ini file with the version provided by the new release. New defaults sometimes contain mandatory changes to enable default functionality. Always places your customization in etc/local.ini or any etc/local.d/*.ini file.
(I was followed this and it worked)
https://docs.couchdb.org/en/3.0.0/install/upgrading.html
I am trying to install OpenIMSCore and following the steps from this link and I am getting the below error when trying to restart the network,
root#ubuntu16:~/.test/OpenIMSCore# /etc/init.d/networking restart
[....] Restarting networking (via systemctl): networking.serviceJob for networking.service failed because the control process exited with error code. See "systemctl status networking.service" and "journalctl -xe" for details.
failed!
root#ubuntu16:~/.test/OpenIMSCore# systemctl status networking.service
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Drop-In: /run/systemd/generator/networking.service.d
└─50-insserv.conf-$network.conf
Active: failed (Result: exit-code) since Sat 2018-08-04 01:17:51 IST; 19s ago
Docs: man:interfaces(5)
Process: 27064 ExecStop=/sbin/ifdown -a --read-environment --exclude=lo (code=exited, status=1/FAILURE)
Process: 27167 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
Process: 27164 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=ex
Main PID: 27167 (code=exited, status=1/FAILURE)
Aug 04 01:17:51 ubuntu16 systemd[1]: Starting Raise network interfaces...
Aug 04 01:17:51 ubuntu16 sh[27164]: /etc/network/interfaces:4: option with empty value
Aug 04 01:17:51 ubuntu16 sh[27164]: ifquery: couldn't read interfaces file "/etc/network/interfaces"
Aug 04 01:17:51 ubuntu16 ifup[27167]: /etc/network/interfaces:4: option with empty value
Aug 04 01:17:51 ubuntu16 ifup[27167]: /sbin/ifup: couldn't read interfaces file "/etc/network/interfaces"
Aug 04 01:17:51 ubuntu16 systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Aug 04 01:17:51 ubuntu16 systemd[1]: Failed to start Raise network interfaces.
Aug 04 01:17:51 ubuntu16 systemd[1]: networking.service: Unit entered failed state.
Aug 04 01:17:51 ubuntu16 systemd[1]: networking.service: Failed with result 'exit-code'.
After debugging I found that the issue was with the /etc/network/interfaces file, when added the below params (from DEVICE, HWADDR to PEERDNS) and start the network I am getting the above error.
Did anyone face the same issues while modifying the interfaces file (my /etc/hosts file & /etc/resolv.conf file are similar to the once provided in the above link).
Any reference on this would also be of great help !
Thanks in advance.
You'll probably kick yourself, but you've got the same typo on two lines. It should be iface eth0 inet dhcp not dchp.
ifup and ifdown will break if they can't parse the file.
When i am trying to start the logstash as a service in centos 7 i am getting below error all the time. I am not a great linux guy, so any help with the start-limit error would be a great help. I tried to follow some links to fix or reset the StartLimitInterval etc, but in vain.
[root#resource-managers logstash-5.1.1]# service logstash status
Logstash Daemon● logstash.service - logstash
Loaded: loaded (/etc/systemd/system/logstash.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Wed 2017-02-01 17:49:11 UTC; 741ms ago
Process: 8562 ExecStart=/home/centos/logstash-5.1.1/bin/logstash --path.settings /home/centos/logstash-5.1.1/config (code=exited, status=217/USER)
Main PID: 8562 (code=exited, status=217/USER)
Feb 01 17:49:11 resource-managers.cisco.com systemd[1]: Unit logstash.service entered failed state.
Feb 01 17:49:11 resource-managers.cisco.com systemd[1]: logstash.service failed.
Feb 01 17:49:11 resource-managers.cisco.com systemd[1]: logstash.service holdoff time over, schedulin...rt.
Feb 01 17:49:11 resource-managers.cisco.com systemd[1]: start request repeated too quickly for logsta...ice
Feb 01 17:49:11 resource-managers.cisco.com systemd[1]: Failed to start logstash.
Feb 01 17:49:11 resource-managers.cisco.com systemd[1]: Unit logstash.service entered failed state.
Feb 01 17:49:11 resource-managers.cisco.com systemd[1]: logstash.service failed.
Regards,
Kiran
I met the same problem, and solved it. Maybe it can help you.
Can you check your ${LS_HOME}/config/startup.options file? You should set LC_USER and LC_GROUP to existed account and group .
# user and group id to be invoked as
LS_USER=elk-test
LS_GROUP=elk-test
In my system, I changed the default value "logstash" to "elk-etst".
After that, ran the system-install command, and started the service, it worked!
● logstash.service - logstash
Loaded: loaded (/etc/systemd/system/logstash.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2017-02-05 11:10:04 CST; 8s ago
Main PID: 7395 (java)
CGroup: /system.slice/logstash.service
└─7395 /usr/bin/java -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+DisableExplicitGC -Djava.awt.headless=true -Df...
ps: I'm running logstash-5.1.2