Please ignore the following error about deb-systemd-helper not finding samba-ad-dc.service
up vote
-1
down vote
favorite
when i try to upgrade its come an i dont know how to resolve this
shashank@shashank-H110M-S2:~$ sudo apt install apt
[sudo] password for shashank:
Reading package lists... Done
Building dependency tree
Reading state information... Done
apt is already the newest version (1.6.6).
The following packages were automatically installed and are no longer required:
linux-headers-4.15.0-34 linux-headers-4.15.0-34-generic
linux-image-4.15.0-34-generic linux-modules-4.15.0-34-generic
linux-modules-extra-4.15.0-34-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.2) ...
Samba is not being run as an AD Domain Controller.
Please ignore the following error about deb-systemd-helper not finding samba-ad-dc.service.
Job for nmbd.service failed because a timeout was exceeded.
See "systemctl status nmbd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript nmbd, action "start" failed.
● nmbd.service - Samba NMB Daemon
Loaded: loaded (/lib/systemd/system/nmbd.service; disabled; vendor preset: enabled)
Active: failed (Result: timeout) since Mon 2018-11-12 13:21:42 IST; 19ms ago
Docs: man:nmbd(8)
man:samba(7)
man:smb.conf(5)
Process: 6648 ExecStart=/usr/sbin/nmbd --foreground --no-process-group $NMBDOPTIONS (code=killed, signal=TERM)
Main PID: 6648 (code=killed, signal=TERM)
Status: "nmbd: No local IPv4 non-loopback interfaces available, waiting for interface ..."
Nov 12 13:20:12 shashank-H110M-S2 systemd[1]: Starting Samba NMB Daemon...
Nov 12 13:21:42 shashank-H110M-S2 systemd[1]: nmbd.service: Start operation timed out. Terminating.
Nov 12 13:21:42 shashank-H110M-S2 systemd[1]: nmbd.service: Failed with result 'timeout'.
Nov 12 13:21:42 shashank-H110M-S2 systemd[1]: Failed to start Samba NMB Daemon.
dpkg: error processing package samba (--configure):
installed samba package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Errors were encountered while processing:
samba
E: Sub-process /usr/bin/dpkg returned an error code (1)
samba windows-subsystem-for-linux
asked Nov 12 at 8:02
ShivShanku
12
add a comment |
up vote
-1
down vote
favorite
when i try to upgrade its come an i dont know how to resolve this
shashank@shashank-H110M-S2:~$ sudo apt install apt
[sudo] password for shashank:
Reading package lists... Done
Building dependency tree
Reading state information... Done
apt is already the newest version (1.6.6).
The following packages were automatically installed and are no longer required:
linux-headers-4.15.0-34 linux-headers-4.15.0-34-generic
linux-image-4.15.0-34-generic linux-modules-4.15.0-34-generic
linux-modules-extra-4.15.0-34-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.2) ...
Samba is not being run as an AD Domain Controller.
Please ignore the following error about deb-systemd-helper not finding samba-ad-dc.service.
Job for nmbd.service failed because a timeout was exceeded.
See "systemctl status nmbd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript nmbd, action "start" failed.
● nmbd.service - Samba NMB Daemon
Loaded: loaded (/lib/systemd/system/nmbd.service; disabled; vendor preset: enabled)
Active: failed (Result: timeout) since Mon 2018-11-12 13:21:42 IST; 19ms ago
Docs: man:nmbd(8)
man:samba(7)
man:smb.conf(5)
Process: 6648 ExecStart=/usr/sbin/nmbd --foreground --no-process-group $NMBDOPTIONS (code=killed, signal=TERM)
Main PID: 6648 (code=killed, signal=TERM)
Status: "nmbd: No local IPv4 non-loopback interfaces available, waiting for interface ..."
Nov 12 13:20:12 shashank-H110M-S2 systemd[1]: Starting Samba NMB Daemon...
Nov 12 13:21:42 shashank-H110M-S2 systemd[1]: nmbd.service: Start operation timed out. Terminating.
Nov 12 13:21:42 shashank-H110M-S2 systemd[1]: nmbd.service: Failed with result 'timeout'.
Nov 12 13:21:42 shashank-H110M-S2 systemd[1]: Failed to start Samba NMB Daemon.
dpkg: error processing package samba (--configure):
installed samba package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Errors were encountered while processing:
samba
E: Sub-process /usr/bin/dpkg returned an error code (1)
samba windows-subsystem-for-linux
asked Nov 12 at 8:02
ShivShanku
12
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
when i try to upgrade its come an i dont know how to resolve this
shashank@shashank-H110M-S2:~$ sudo apt install apt
[sudo] password for shashank:
Reading package lists... Done
Building dependency tree
Reading state information... Done
apt is already the newest version (1.6.6).
The following packages were automatically installed and are no longer required:
linux-headers-4.15.0-34 linux-headers-4.15.0-34-generic
linux-image-4.15.0-34-generic linux-modules-4.15.0-34-generic
linux-modules-extra-4.15.0-34-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.2) ...
Samba is not being run as an AD Domain Controller.
Please ignore the following error about deb-systemd-helper not finding samba-ad-dc.service.
Job for nmbd.service failed because a timeout was exceeded.
See "systemctl status nmbd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript nmbd, action "start" failed.
● nmbd.service - Samba NMB Daemon
Loaded: loaded (/lib/systemd/system/nmbd.service; disabled; vendor preset: enabled)
Active: failed (Result: timeout) since Mon 2018-11-12 13:21:42 IST; 19ms ago
Docs: man:nmbd(8)
man:samba(7)
man:smb.conf(5)
Process: 6648 ExecStart=/usr/sbin/nmbd --foreground --no-process-group $NMBDOPTIONS (code=killed, signal=TERM)
Main PID: 6648 (code=killed, signal=TERM)
Status: "nmbd: No local IPv4 non-loopback interfaces available, waiting for interface ..."
Nov 12 13:20:12 shashank-H110M-S2 systemd[1]: Starting Samba NMB Daemon...
Nov 12 13:21:42 shashank-H110M-S2 systemd[1]: nmbd.service: Start operation timed out. Terminating.
Nov 12 13:21:42 shashank-H110M-S2 systemd[1]: nmbd.service: Failed with result 'timeout'.
Nov 12 13:21:42 shashank-H110M-S2 systemd[1]: Failed to start Samba NMB Daemon.
dpkg: error processing package samba (--configure):
installed samba package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Errors were encountered while processing:
samba
E: Sub-process /usr/bin/dpkg returned an error code (1)
samba windows-subsystem-for-linux
asked Nov 12 at 8:02
ShivShanku
12
when i try to upgrade its come an i dont know how to resolve this
shashank@shashank-H110M-S2:~$ sudo apt install apt
[sudo] password for shashank:
Reading package lists... Done
Building dependency tree
Reading state information... Done
apt is already the newest version (1.6.6).
The following packages were automatically installed and are no longer required:
linux-headers-4.15.0-34 linux-headers-4.15.0-34-generic
linux-image-4.15.0-34-generic linux-modules-4.15.0-34-generic
linux-modules-extra-4.15.0-34-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.2) ...
Samba is not being run as an AD Domain Controller.
Please ignore the following error about deb-systemd-helper not finding samba-ad-dc.service.
Job for nmbd.service failed because a timeout was exceeded.
See "systemctl status nmbd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript nmbd, action "start" failed.
● nmbd.service - Samba NMB Daemon
Loaded: loaded (/lib/systemd/system/nmbd.service; disabled; vendor preset: enabled)
Active: failed (Result: timeout) since Mon 2018-11-12 13:21:42 IST; 19ms ago
Docs: man:nmbd(8)
man:samba(7)
man:smb.conf(5)
Process: 6648 ExecStart=/usr/sbin/nmbd --foreground --no-process-group $NMBDOPTIONS (code=killed, signal=TERM)
Main PID: 6648 (code=killed, signal=TERM)
Status: "nmbd: No local IPv4 non-loopback interfaces available, waiting for interface ..."
Nov 12 13:20:12 shashank-H110M-S2 systemd[1]: Starting Samba NMB Daemon...
Nov 12 13:21:42 shashank-H110M-S2 systemd[1]: nmbd.service: Start operation timed out. Terminating.
Nov 12 13:21:42 shashank-H110M-S2 systemd[1]: nmbd.service: Failed with result 'timeout'.
Nov 12 13:21:42 shashank-H110M-S2 systemd[1]: Failed to start Samba NMB Daemon.
dpkg: error processing package samba (--configure):
installed samba package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Errors were encountered while processing:
samba
E: Sub-process /usr/bin/dpkg returned an error code (1)
samba windows-subsystem-for-linux
samba windows-subsystem-for-linux
asked Nov 12 at 8:02
ShivShanku
12
asked Nov 12 at 8:02
ShivShanku
12
asked Nov 12 at 8:02
ShivShanku
12
asked Nov 12 at 8:02
ShivShanku
12
asked Nov 12 at 8:02
ShivShanku
12
12
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
I had the same issue, but with the lattes update I uninstalled an reinstalled everything and now it works fine.
Hope it helps you
answered Dec 1 at 12:31
user898874
1
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I had the same issue, but with the lattes update I uninstalled an reinstalled everything and now it works fine.
Hope it helps you
answered Dec 1 at 12:31
user898874
1
add a comment |
up vote
0
down vote
I had the same issue, but with the lattes update I uninstalled an reinstalled everything and now it works fine.
Hope it helps you
answered Dec 1 at 12:31
user898874
1
add a comment |
up vote
0
down vote
up vote
0
down vote
I had the same issue, but with the lattes update I uninstalled an reinstalled everything and now it works fine.
Hope it helps you
answered Dec 1 at 12:31
user898874
1
I had the same issue, but with the lattes update I uninstalled an reinstalled everything and now it works fine.
Hope it helps you
answered Dec 1 at 12:31
user898874
1
answered Dec 1 at 12:31
user898874
1
answered Dec 1 at 12:31
user898874
1
answered Dec 1 at 12:31
user898874
1
1
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1092145%2fplease-ignore-the-following-error-about-deb-systemd-helper-not-finding-samba-ad%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
