Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I have this simple /etc/systemd/system/test.service file
[Unit]
Description=SkriptA
After=network.target auditd.service
[Service]
Type=simple
ExecStart=/opt/test.sh
[Install]
WantedBy=multi-user.target
When i run systemctl start test.service and then systemctl status test.service It shows that serivce succeeded but is inacitve, please why is this?
● test1.service - SkriptA
Loaded: loaded (/etc/systemd/system/test1.service; disabled; vendor preset: enabled)
Active: inactive (dead)
Mar 05 12:17:55 hro0078 systemd[1]: Started SkriptA.
Mar 05 12:17:55 hro0078 systemd[1]: test1.service: Succeeded.
The ExecStart script is simple as service
#!/usr/bin/bash
echo Hi > /tmp/test1
date >> /tmp/test1
I use: Linux version 4.19.0-13-amd64 (debian-kernel#lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.160-2 (2020-11-28)
Your program was started successfully and it terminated directly.
To have your service active, it needs to keep running. Example:
#!/usr/bin/bash
while [ 1 ]; do
echo Hi > /tmp/test1
date >> /tmp/test1
sleep 60
done
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
On a Windows 10 host I have a VirtualBox virtual machine with Debian 11. The access to the VM is done by a virtual network card "Virtual Box Host Only Ethernet Adaptater".
I connect with ssh on my VM without any problem.
I have a shared folder on Windows 10, and I want to access it via a mount from my VM. I've been doing this for years, but now I can't get a stable behavior. It worked last week, but now it doesn't work anymore
I use this command:
mount -a -t cifs //192.168.56.1/vmjpweb /home/web -o "username=*******,password=*******" --verbose
The result :
/ : ignoré
none : ignoré
/media/cdrom0 : ignoré
domain=192.168.56.1
password specified twice, ignoring second
mount.cifs kernel mount options: ip=192.168.56.1,unc=\\192.168.56.1\vmjpweb,vers=3.0,sec=ntlmsspi,uid=33,gid=33,user=*******,domain=192.168.56.1,pass=********
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
The kernel log:
Oct 31 09:11:49 rock kernel: [ 1009.046835] CIFS: Attempting to mount //192.168.56.1/vmjpweb
Oct 31 09:11:49 rock kernel: [ 1009.221195] CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Oct 31 09:11:49 rock kernel: [ 1009.221219] CIFS: VFS: \\192.168.56.1 Send error in SessSetup = -13
Oct 31 09:11:49 rock kernel: [ 1009.221263] CIFS: VFS: cifs_mount failed w/return code = -13
I just created a new local user and it works well.
The login I was using was not local on the host, but on the domain of my work. I was trying to connect to the shared folder without a connection to the domain.
I also use fstab for the running.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I am trying to start apache2 services by running-
sudo service apache2 start
But it is resulting in-
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.
I tried-
sudo systemctl status apache2.service
and it's showing-
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2020-12-08 11:17:18 IST; 7min ago
Docs: https://httpd.apache.org/docs/2.4/
Process: 30529 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
Dec 08 11:17:18 dk systemd[1]: Starting The Apache HTTP Server...
Dec 08 11:17:18 dk apachectl[30535]: chown: invalid user: 'dk'
Dec 08 11:17:18 dk systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
Dec 08 11:17:18 dk systemd[1]: apache2.service: Failed with result 'exit-code'.
Dec 08 11:17:18 dk systemd[1]: Failed to start The Apache HTTP Server.
I am assuming the problem is with invalid user: dk. How can i resolve this?
Also I recently removed one user account which already had LAMP stack installed. Is that the reason why it's showing invalid user?
In new systems, e.g. ubuntu 20 * LTS, the configuration file is /etc/apache2/envvars
look for APACHE_RUN_USER and APACHE_RUN_GROUP.
You must see in the file:
/etc/apache2/apache2.conf
or
/etc/apache2/httpd.conf
what is the entered user and what group
normally it is:
User www-data
Group www-data
or maybe in your case it is "dk"
in addition, you may have specified in the server file that the site location is in a directory owned by "dk".
Check the server configuration with the command:
apachectl configtest
or
sudo apachectl configtest
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I've created this service in /etc/systemd/system/webapp.service
in a
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
This is the content:
[Unit]
Description=webapp daemon
After=network.target
[Service]
Type=notify
ExecStart=/usr/local/bin/start-webapp.sh
ExecStop=/usr/local/bin/stop-webapp.sh
ExecReload=/usr/local/bin/reload-webapp.sh
StandardOutput=null
[Install]
WantedBy=multi-user.target
Alias=webapp.service
I try to startd the service using:
sudo systemctl start webapp.service
But when I do
sudo systemctl status webapp.service
I got this error:
● webapp.service - webapp daemon
Loaded: loaded (/etc/systemd/system/webapp.service; disabled; vendor preset: enabled)
Active: inactive (dead)
Jun 01 11:31:48 localhost systemd[1]: /etc/systemd/system/webapp.service:8: Missing '='.
Jun 01 11:31:52 localhost systemd[1]: /etc/systemd/system/webapp.service:8: Missing '='.
Jun 01 11:35:21 localhost systemd[1]: /etc/systemd/system/webapp.service:8: Missing '='.
Jun 01 11:35:31 localhost systemd[1]: /etc/systemd/system/webapp.service:8: Missing '='.
and
admin#localhost:/etc/systemd/system$ cat -vetn webapp.service
1 [Unit]$
2 Description=webapp daemon$
3 [Service]$
4 Type=simple$
5 ExecStart=/usr/local/bin/start-webapp.sh$
6 ExecStop=/usr/local/bin/stop-webapp.sh$
7 ExecReload=/usr/local/bin/reload-webapp.sh$
8 [Install]$
9 WantedBy=multi-user.target$
Your config content seems nothing wrong, so I have copied it to my debian server and try to run it, and it's really ok.
But it's strange that the stdout of cat -vetn webapp.service is not the exactly content of your original config, so would you mind to remove the original config and do it again ?
refer: https://wiki.debian.org/systemd/Services
redo:
mv webapp.service /tmp/webapp.service
vi webapp.service # check characters
After creating or modifying any unit files, we must tell systemd that we want it to look for new things:
systemctl daemon-reload
Then, tell systemd to enable it, so that it will start every time we boot:
systemctl enable myservice.service
Finally, start it:
systemctl start myservice.service
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed last year.
The community reviewed whether to reopen this question last year and left it closed:
Original close reason(s) were not resolved
Improve this question
rfkill list 1
command gives me:
1: ideapad_bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
However, when I run the following command,
sudo systemctl status bluetooth.service
I get this error:
bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2019-01-27 13:55:21 +03; 1h 4min ago
Docs: man:bluetoothd(8)
Main PID: 950 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
CGroup: /system.slice/bluetooth.service
└─950 /usr/lib/bluetooth/bluetoothd
systemd[1]: Starting Bluetooth service...
bluetoothd[950]: Starting SDP server
systemd[1]: Started Bluetooth service.
bluetoothd[950]: Bluetooth management interface 1.14 initialized
bluetoothd[950]: Failed to set mode: Blocked through rfkill (0x12)
bluetoothd[950]: Failed to set mode: Blocked through rfkill (0x12)
bluetoothd[950]: Failed to set mode: Blocked through rfkill (0x12)
bluetoothd[950]: Failed to set mode: Blocked through rfkill (0x12)
bluetoothd[950]: Failed to set mode: Blocked through rfkill (0x12)
bluetoothd[950]: Failed to set mode: Failed (0x03)
I use Ubuntu 18.04.1 LTS. When I start bluetooth, it searches for the devices, but it never finishes.
I currently have this problem in Mint 19.3 (kernel 5.4.0-48-generic) on an X1 Carbon ThinkPad. My rfkill showed Bluetooth as Hard blocked. No idea why the following is necessary, but it worked for me:
sudo rfkill unblock bluetooth
I've had to do it twice in the last two weeks, which suggests something random is happening that results in Bluetooth being blocked after a restart. Random issues are always a hoot.
I had the same problem : rfkill did not show the device as blocked but the commands
# rfkill block bluetooth
# rfkill unblock bluetooth
worked for me.
I hope I was helpful
PS : the # means run as root (via sudo or directly logged in as the root user)
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I just installed MongoDb on Ubuntu 16.04 and I can not run the server. I get the following information when the "status" of the server (sudo systemctl start mongodb):
lmunoz#lmunoz:/var/www/node/dashboard$ sudo systemctl status mongodb
● mongodb.service - High-performance, schema-free document-oriented
database
Loaded: loaded (/etc/systemd/system/mongodb.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since mar 2017-05-09 12:01:59 PET;
29s ago
Process: 1042 ExecStart=/usr/bin/mongod --quiet --config
/etc/mongod.conf (code=exited, status=48)
Main PID: 1042 (code=exited, status=48)
may 09 12:01:59 lmunoz systemd[1]: Started High-performance, schema-
free document-oriented database.
may 09 12:01:59 lmunoz systemd[1]: mongodb.service: Main process
exited, code=exited, status=48/n/a
may 09 12:01:59 lmunoz systemd[1]: mongodb.service: Unit entered
failed state.
may 09 12:01:59 lmunoz systemd[1]: mongodb.service: Failed with result
'exit-code'.
The log (/var/log/mongodb/mongod.log) shows me the following:
listen(): bind() failed errno:98 Address already in use for socket:
127.0.0.1:27017
addr already in use
Failed to set up sockets during startup.
dbexit: rc: 48
And my configuration file (/etc/systemd/system/mongodb.service) contains:
[Unit]
Description=High-performance, schema-free document-oriented database
After=network.target
[Service]
User=mongodb
ExecStart=/usr/bin/mongod --quiet --config /etc/mongod.conf
[Install]
WantedBy=multi-user.target
Look at the logs you are having another service which is running on the port 27017.
Look for that service and stop it and then retry. Or if you don't care about the service running on that port, can do
sudo fuser -k 27017/tcp
Another alternative will be to change the default of mongodb. See mongodb how to change default port