package samba 2:4.5.8+dfsg-0ubuntu0.17.04.3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[José Caldas Gois Júnior]

When i login the system display a message error box

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: samba 2:4.5.8+dfsg-0ubuntu0.17.04.3
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Fri Jul 14 04:45:05 2017
ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1
InstallationDate: Installed on 2017-05-15 (59 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt 1.4
SambaServerRegression: Yes
SmbConfIncluded: Yes
SmbLog:

SourcePackage: samba
Title: package samba 2:4.5.8+dfsg-0ubuntu0.17.04.3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
UpgradeStatus: No upgrade log present (probably fresh install)
WindowsFailedConnect: Yes

[Seth Arnold (seth-arnold)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Seth Arnold (seth-arnold)]

This looks like the relevant portion of the logs:

Configurando samba (2:4.5.8+dfsg-0ubuntu0.17.04.3) ...
Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.
/usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory
Job for nmbd.service failed because a timeout was exceeded.

Thanks

[Andreas Hasenack (ahasenack)]

No, that is just noise unfortunately. This is the real error:
   Status: "nmbd: No local IPv4 non-loopback interfaces available, waiting for interface ..."

So nmbd failed to start because it didn't find an IPv4 interface that's not "lo".

It does look like you have network configuration problems. From the nmbd logs:
Packet send failed to 192.168.0.255(138) ERRNO=Argumento inválido
Packet send failed to 192.168.0.255(137) ERRNO=A rede está fora de alcance
send_netbios_packet: send_packet() to IP 192.168.0.255 port 137 failed

Could you please check your IP, netmask, default gateway and broadcast addresses? The nmbd daemon needs to be able to send data to the broadcast address but it doesn't look like 192.168.0.255 is that address for the LAN segment you are in.

[José Caldas Gois Júnior (goisjr)]

Thanks !!

[image: logo]

*José Caldas Gois Jr.* *Advogado* *, Caldas Gois Advogados Associados*
Tel: [phone] | Mobile: [phone]
<email address hidden> | www.cgadv.com.br
[image: Facebook]
<http://s.wisestamp.com/links?url=https%3A%2F%2Fwww.facebook.com%2Fgoisjr>
[image:
LinkedIn]
<http://s.wisestamp.com/links?url=http%3A%2F%2Fbr.linkedin.com%2Fpub%2Fjos%25C3%25A9-caldas-gois-j%25C3%25BAnior%2F22%2F82%2F453>
 [image: Flickr]
<http://s.wisestamp.com/links?url=http%3A%2F%2Fwww.flickr.com%2Fphotos%2Fgoisjr>

2017-07-14 16:45 GMT-03:00 Andreas Hasenack <email address hidden>:

> No, that is just noise unfortunately. This is the real error:
> Status: "nmbd: No local IPv4 non-loopback interfaces available, waiting
> for interface ..."
>
> So nmbd failed to start because it didn't find an IPv4 interface that's
> not "lo".
>
> It does look like you have network configuration problems. From the nmbd
> logs:
> Packet send failed to 192.168.0.255(138) ERRNO=Argumento inválido
> Packet send failed to 192.168.0.255(137) ERRNO=A rede está fora de alcance
> send_netbios_packet: send_packet() to IP 192.168.0.255 port 137 failed
>
> Could you please check your IP, netmask, default gateway and broadcast
> addresses? The nmbd daemon needs to be able to send data to the
> broadcast address but it doesn't look like 192.168.0.255 is that address
> for the LAN segment you are in.
>
> ** Changed in: samba (Ubuntu)
> Status: New => Incomplete
>
> ** No longer affects: init-system-helpers (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1704394
>
> Title:
> package samba 2:4.5.8+dfsg-0ubuntu0.17.04.3 failed to install/upgrade:
> sub-processo script post-installation instalado retornou estado de
> saída de erro 1
>
> Status in samba package in Ubuntu:
> Incomplete
>
> Bug description:
> When i login the system display a message error box
>
> ProblemType: Package
> DistroRelease: Ubuntu 17.04
> Package: samba 2:4.5.8+dfsg-0ubuntu0.17.04.3
> ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
> Uname: Linux 4.10.0-26-generic x86_64
> ApportVersion: 2.20.4-0ubuntu4.1
> Architecture: amd64
> Date: Fri Jul 14 04:45:05 2017
> ErrorMessage: sub-processo script post-installation instalado retornou
> estado de saída de erro 1
> InstallationDate: Installed on 2017-05-15 (59 days ago)
> InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
> RelatedPackageVersions:
> dpkg 1.18.10ubuntu2
> apt 1.4
> SambaServerRegression: Yes
> SmbConfIncluded: Yes
> SmbLog:
>
> SourcePackage: samba
> Title: package samba 2:4.5.8+dfsg-0ubuntu0.17.04.3 failed to
> install/upgrade: sub-processo script post-installation instalado retornou
> estado de saída de erro 1
> UpgradeStatus: No upgrade log present (probably fresh install)
> WindowsFailedConnect: Yes
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/samba/+bug/
> 1704394/+subscriptions
>

[Andreas Hasenack (ahasenack)]

Did you solve your problem?

[Launchpad Janitor (janitor)]

[Expired for samba (Ubuntu) because there has been no activity for 60 days.]