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.
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 last year.
Improve this question
I upgraded current OS to latest version. i am unable to do su from admin to root user.
I checked /etc/password, /etc/shadow, unix_chkpwd and su permission, everything looks ok
i dig into the /etc/pam.d/ configuration made some changes to see if any luck, but none of them worked.
Below is the error log i can see in system logs, it would be great if any one help on this issue
Note: I am able to telnet to root.
unix_chkpwd[7868]:, check pass; user unknown
unix_chkpwd[7868]:, password check failed for user (root)
su[7279]:, pam_unix(su:auth): authentication failure; logname= uid=2000 euid=2000 tty=/dev/pts/3 ruser=admin rhost= user=root
unix_chkpwd[7874]:, check pass; user unknown
unix_chkpwd[7876]:, check pass; user unknown
unix_chkpwd[7876]:, password check failed for user (root)
su[7279]:, pam_authenticate: Authentication failure
su[7279]:, PAM 1 more authentication failure; logname= uid=2000 euid=2000 tty=/dev/pts/3 ruser=admin rhost= user=root
su[7279]:, FAILED su for root by admin
su[7279]:, su session not logged to /var/log/sulog
su[7279]:, - /dev/pts/3 admin:root
in a new machine root might not have a password
try sudo su
or sudo passwd root
for more info you can see this page
https://askubuntu.com/questions/347818/what-is-the-default-root-password-when-was-never-set-at-installation-time
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
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 6 years ago.
Improve this question
I am having issues using VNC between MacOS X and Linux.
I installed tightvnc server on CentOS Linux and vncviewer on Mac OS X. I have done all the setting to my best knowledge and then started vncserver on the Linux computer. I also opened the port 5901.
When I execute the command "vncviewer :1" on the Linux machine, things work fine. I can see desktop appear in a window.
From Mac OS X I am unable to connect to the Linux vncserver. The message I get is
"The connection was refused by the computer"
I am able to SSH from Mac to Linux so there is connection between the two computers but VNC won't work.
Can someone please help me save this issue. I have searched the web but found nothing that worked thus far.
Thanks!
Here is the message from the vnc log file.
Xvnc TigerVNC 1.1.0 - built May 11 2016 13:01:55
Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 11704000, The X.Org Foundation
Tue Jan 24 10:03:36 2017
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5901
vncext: Listening for HTTP connections on all interface(s), port 5801
vncext: created VNC server for screen 0
GNOME_KEYRING_SOCKET=/tmp/keyring-jWrQoB/socket
SSH_AUTH_SOCK=/tmp/keyring-jWrQoB/socket.ssh
GNOME_KEYRING_PID=7644
gnome-session[7629]: WARNING: Could not launch application 'linc-cleanup-sockets.desktop': Unable to start application: Failed to execute
child process "/usr/bin/linc-cleanup-sockets" (No such file or directory)
Failed to play sound: File or data not found
(polkit-gnome-authentication-agent-1:7668): GLib-GObject-WARNING **: cannot register existing type `_PolkitError'
(polkit-gnome-authentication-agent-1:7668): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
An instance of nm-applet is already running.
Dropbox isn't running!
Dropbox is already running!
Initializing nautilus-dropbox 2015.10.28
(null): Warning no default label for /home/amit/.gvfs
Failure: Module initalization failed
** (gnome-panel:7657): WARNING **: panel-applet-frame.c:1288: failed to load applet OAFIID:GnoteApplet:
(null)
You can tunnel the VNC connection through SSH by using local port forwarding.
To start the port forward:
ssh -NTf -L 5901:localhost:5901 user#linux_server
Then point your VNC viewer at localhost.
vncviewer localhost:5901