Shadow.service fails after LightDM uninstall

Hi,
Since I've uninstalled Light-locker (and LightDM as a dependency) I receive the following error:
● shadow.service - Verify integrity of password and group files
Loaded: loaded (/usr/lib/systemd/system/shadow.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since di 2015-03-24 19:43:48 CET; 45min ago
Process: 315 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
Main PID: 315 (code=exited, status=2)
mrt 24 19:43:47 zeus pwck[315]: user 'lightdm': directory '/var/lib/lightdm' does not exist
mrt 24 19:43:48 zeus pwck[315]: pwck: no changes
mrt 24 19:43:48 zeus systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
mrt 24 19:43:48 zeus systemd[1]: Failed to start Verify integrity of password and group files.
mrt 24 19:43:48 zeus systemd[1]: Unit shadow.service entered failed state.
mrt 24 19:43:48 zeus systemd[1]: shadow.service failed.
Can anyone help me fix this?
Thanks in advance!
Last edited by VenomGameworld (2015-03-24 18:35:15)

Spider.007 wrote:It's interesting the package creates the user on install, but doesn't remove it on uninstallation. I wonder if this is intended by the maintainer.
https://projects.archlinux.org/svntogit … de9766105a is the change that removed user and group deletion.

Similar Messages

[Solved] Mismatch on GID and shadow.service fails

Hi, randomly the shadow.service fails on loading and it gives me this output:
$ systemctl status shadow.service
● shadow.service - Verify integrity of password and group files
Loaded: loaded (/usr/lib/systemd/system/shadow.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since sab 2015-03-28 14:54:50 CET; 13min ago
Process: 1988 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
Main PID: 1988 (code=exited, status=2)
mar 28 14:54:50 vivopicenin pwck[1988]: user 'git': no group 999
mar 28 14:54:50 vivopicenin pwck[1988]: user 'systemd-journal-remote': no group 998
mar 28 14:54:50 vivopicenin pwck[1988]: user 'systemd-journal-upload': no group 997
mar 28 14:54:50 vivopicenin pwck[1988]: user 'sddm': no group 996
mar 28 14:54:50 vivopicenin pwck[1988]: user 'rtkit': no group 133
mar 28 14:54:50 vivopicenin pwck[1988]: pwck: nessuna modifica
mar 28 14:54:50 vivopicenin systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
mar 28 14:54:50 vivopicenin systemd[1]: Failed to start Verify integrity of password and group files.
mar 28 14:54:50 vivopicenin systemd[1]: Unit shadow.service entered failed state.
mar 28 14:54:50 vivopicenin systemd[1]: shadow.service failed.
The output instead of pwck is:
$ sudo pwck
user 'polkitd': no group 102
user 'avahi': no group 84
user 'colord': no group 124
user 'git': no group 999
user 'systemd-journal-remote': no group 998
user 'systemd-journal-upload': no group 997
user 'sddm': no group 996
user 'rtkit': no group 133
pwck: nessuna modifica
So for example for sddm group it requires a 996 GID, but on my /etc/group file i have this content:
$ cat /etc/group
root:x:0:root
bin:x:1:root,bin,daemon
daemon:x:2:root,bin,daemon
sys:x:3:root,bin
adm:x:4:root,daemon
tty:x:5:
disk:x:6:root
lp:x:7:daemon
mem:x:8:
kmem:x:9:
wheel:x:10:root,marco
ftp:x:11:
mail:x:12:
uucp:x:14:
log:x:19:root
utmp:x:20:
locate:x:21:
rfkill:x:24:
smmsp:x:25:
proc:x:26:
http:x:33:
games:x:50:
lock:x:54:
uuidd:x:68:
dbus:x:81:
network:x:90:
video:x:91:
audio:x:92:
optical:x:93:
floppy:x:94:
storage:x:95:
scanner:x:96:
input:x:97:
power:x:98:
nobody:x:99:
users:x:100:
systemd-journal:x:190:
systemd-journal-gateway:x:191:
systemd-timesync:x:192:
systemd-network:x:193:
systemd-bus-proxy:x:194:
systemd-resolve:x:195:
systemd-journal-upload:x:994:
systemd-journal-remote:x:995:
ntp:x:87:
mysql:x:89:
git:x:993:
usbmux:x:140:
vboxusers:x:108:
sddm:x:992:
There are some mismatches, for example on sddm group which requires 996 GID but on my system i have GID 992.
What should i do in oder to fix it?
Thanks!
P.s. sudo gpwck gives me no output and i don't have any .pacnew on my system.
Last edited by toketin (2015-03-29 17:18:03)

Hi thanks for the reply, i've fixed fot the half of the groups' errors, for the others it gives me that the group X doesn't exist. This the output:
# groupmod --gid 102 polkitd
groupmod: group 'polkitd' does not exist
# groupmod --gid 84 avahi
groupmod: group 'avahi' does not exist
# groupmod --gid 124 colord
groupmod: group 'colord' does not exist
# groupmod --gid 133 rtkit
groupmod: group 'rtkit' does not exist
I had tried to re-install yesterday for example git and sddm packages but it didn't fix the issue.
Last edited by toketin (2015-03-29 12:38:01)

[SOLVED] shadow.service fails

I haven't been tweaking my system much lately, both because it is set up the way I like it and because I haven't been actively interested in it lately. Today I noticed at boot that shadow.service failed. I have updated systemd yesterday and I'm pretty sure this issue popped up only now. It does not seem to cause problems with logging in.
Further inquiry gives me:
systemctl status shadow.service
● shadow.service - Verify integrity of password and group files
Loaded: loaded (/usr/lib/systemd/system/shadow.service; static)
Active: failed (Result: exit-code) since Thu 2014-04-17 09:50:07 CEST; 6min ago
Process: 5847 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
Main PID: 5847 (code=exited, status=2)
Apr 17 09:50:07 hostname pwck[5847]: duplicate password entry
Apr 17 09:50:07 hostname pwck[5847]: delete line 'uuidd:x:68:68:uuidd:/:/sbin/nologin'? No
Apr 17 09:50:07 hostname pwck[5847]: user 'uuidd': no group 68
Apr 17 09:50:07 hostname pwck[5847]: duplicate password entry
Apr 17 09:50:07 hostname pwck[5847]: delete line 'uuidd:x:998:998::/:/sbin/nologin'? No
Apr 17 09:50:07 hostname pwck[5847]: pwck: no changes
Apr 17 09:50:07 hostname systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 17 09:50:07 hostname systemd[1]: Failed to start Verify integrity of password and group files.
Apr 17 09:50:07 hostname systemd[1]: Unit shadow.service entered failed state.
journalctl -xn
Apr 17 09:23:57 hostname systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
-- Subject: Unit shadow.service has failed
-- Unit shadow.service has failed.
Apr 17 09:23:57 hostname systemd[1]: Unit shadow.service entered failed state.
Apr 17 09:27:28 hostname dbus[352]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.15" (uid=1000 pid=5525 comm="systemctl start shadow.service ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
Apr 17 09:27:31 hostname sudo[5527]: username : TTY=pts/0 ; PWD=/home/username ; USER=root ; COMMAND=/usr/bin/systemctl start shadow.service
-- Subject: Unit shadow.service has begun with start-up
-- Unit shadow.service has begun starting up.
Apr 17 09:27:31 hostname systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
-- Subject: Unit shadow.service has failed
-- Unit shadow.service has failed.
Apr 17 09:27:31 hostname systemd[1]: Unit shadow.service entered failed state.
I'm not sure what I'm doing in this field and can't seem to find topics with similar problems to this.
Last edited by D. (2014-04-17 13:04:01)

I've got a similar problem with shadow.service not starting due to invalid password file integrity:
shadow.service - Verify integrity of password and group files
Loaded: loaded (/usr/lib/systemd/system/shadow.service; static)
Active: failed (Result: exit-code) since Sat 2014-04-19 07:40:53 NZST; 22min ago
Process: 289 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
Main PID: 289 (code=exited, status=2)
Apr 19 07:40:53 taniwha-folio13 pwck[289]: user 'rtkit': no group 133
Apr 19 07:40:53 taniwha-folio13 pwck[289]: user 'git': no group 998
Apr 19 07:40:53 taniwha-folio13 pwck[289]: user 'transmission': no group 169
Apr 19 07:40:53 taniwha-folio13 pwck[289]: user 'ntp': no group 87
Apr 19 07:40:53 taniwha-folio13 pwck[289]: user 'uuidd': no group 997
Apr 19 07:40:53 taniwha-folio13 pwck[289]: user 'rpc': no group 32
Apr 19 07:40:53 taniwha-folio13 pwck[289]: pwck: no changes
Apr 19 07:40:53 taniwha-folio13 systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 19 07:40:54 taniwha-folio13 systemd[1]: Failed to start Verify integrity of password and group files.
Apr 19 07:40:54 taniwha-folio13 systemd[1]: Unit shadow.service entered failed state.
In my case, the error message indicates users without groups. How do I address this?
ps similar problem, so not sure if I should start a new thread or not

Shadow.service fails to start

I've gotten a notification upon startup at least twice at this point - something along the lines of "shadow.service failed". systemctl --failed confirms that it's the only service failing.
I found https://bbs.archlinux.org/viewtopic.php?id=180203 - which addresses the same topic, but I'm unsure of how to go about applying the fixes mentioned here. Where can I find the new uuid value that I need for the files that are listed in the first reply? Do I need to edit each of those files? Are there any other files that would affect shadow.service's operation, or any other files that need to be updated with the appropriate uuid value?
The other thing I don't understand is why the service would fail. If the uuid value in the files it checks is invalid, shouldn't it return an error message stating that the checked files failed validation?
Thanks in advance for any help you can provide!

Just read the mentioned thread because the answer is in it and duplicating that seems useless. Don't make it seem like you want the answer to be presented on a silver plate

OBIEE Start/Stop Services failed(After LDAP Configuration)

Hi ,
We made some changes(that is we have added new OID
and configured the new OID based upon the Oracle BI security guide which is in Oracle Site
) to the LDAP configuration in OBIEE web console and it prompted for a restart of the OBIEE services . when we tried restarting the services we are not able to stop all the services . Please find the attached log files .
Note:
1.unable to kill the process ID
which is releated to OBIEE 11.1.1.6.0 services..
2.We have follwed the section 3 in the below link to configure the LDAP : http://docs.oracle.com/cd/E23943_01/bi.1111/e10543/toc.htm.
Please find the below error details in short form and kindly find the attahced file(file name) for more details
Error:
Caused By: oracle.security.jps.service.igf.IGFException: JPS-02597: You configured a custom Authentication Provider or WLS generic LDAPAuthenticator, which the libOvd can not recognize. Supply the idstore.type property in jps-config.xml file, or use a specific WLS LDAP Authentication provider that matches your LDAP server instead of a generic one.
at oracle.security.jps.internal.api.identitystore.IdentityStoreConfigurationUtil.checkIdStoreTypeLater(IdentityStoreConfigurationUtil.java:819)
at oracle.security.jps.internal.api.identitystore.IdentityStoreConfigurationUtil.getLibOvdLdapPushData(IdentityStoreConfigurationUtil.java:524)
at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider$1.run(OvdIGFServiceProvider.java:232)
at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider$1.run(OvdIGFServiceProvider.java:229)
at java.security.AccessController.doPrivileged(Native Method)
Truncated. see log file for complete stacktrace
>
<Jan 29, 2013 6:39:05 AM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jan 29, 2013 6:39:05 AM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jan 29, 2013 6:39:05 AM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state cha
Error Codes
Problem Category/Subcategory
BI EE Platform Administration/Administration Tool
Uploaded Files
File: nohup.zip:134848
Template Question Responses
1) ### Admin Tool version ###
2) Are you running Oracle Business Intelligence Enterprise Edition using virtualization or partitioning technologies (for example, VMWare) ?
No
3) If yes, please provide the product used and its version.
4) ### Documentation Used ###
5) ### Impact on Business ###
Edited by: 919942 on Jan 31, 2013 5:10 AM

"JPS-02597: You configured a custom Authentication Provider or WLS generic LDAPAuthenticator, which the libOvd can not recognize. Supply the idstore.type property in jps-config.xml file, or use a specific WLS LDAP Authentication provider that matches your LDAP server instead of a generic one."
Looks like the config you entered was a tad off. Any chance you can roll back by restoring the original files from before the change?
$FMWH/user_projects/domains/yourdomain/config/config.xml
$FMWH/user_projects/domains/yourdomain/config/fmwconfig/jps-config.xml
In the config.xml, inside the <realm> tag yo ushould find your authenticaiton providers and there's two important things for your new one to check:
1.) xsi-type="wls:..." <-- This should be your OID type rather than a generic (or wrong) one
2.) If you're not 100% sure about the config or don't want to immediately shut out native WLS users or want to retain them (both OID and WLS LDAP considered valid), then PLEASE make sure that you run your new authenticator with <sec:control-flag>SUFFICIENT</sec:control-flag> and don't make it REQUIRED since otherwise you won't be able to bring anything up anymore if a single parameter in the authenticator config is off...
Also, check out what Tony wrote together a while back: http://www.peakindicators.com/index.php/knowledge-base/115-oracle-bi-11g-security-troubleshooting
Update:
Should have read the error message more carefully...looks like you actually just slipped by one line in the authenticator config and chose "OracleVirtualDirectory" instead of "OracleInternetDirectory" since it tries to use the libOvd rather than the OID one.
Edited by: Christian Berg on Jan 31, 2013 2:58 PM

Empsecformat RestFul service fail after update

Hello everybody when I test "empsecformat" sample web service at the first time, it operates OK, but just pressing "Apply Changes" button, web service fail and returns "Error during evaluation of resource template" message and do not runs anymore.
Then I have to "Reset Sample Data" to recover initial situation
I Have
Application Express 4.2.1.00.08
Listener 1.0
I am running Oracle XE 10 over Linux
Thanks

Read the server logs for the current error, concentrating on Apache. That'll usually tell you what isn't working.
Check the Apache configuration file syntax:
apachectl configtest
Verify DNS with the command:
sudo changeip -checkhostname
If you're on a NAT'd network and running local DNS services, stay out of .local and .arpa with the domain you're using, and preferably use a registered domain. If you're NAT'd, don't try to use ISP or Google or other off-network DNS servers, as those do not provide translations for the private-IP-block NAT'd IP addresses you're using.
As for a reset, there's a server setup done file (I don't recall the filename of that off-hand), but I've found removing that file does not reset the entire environment completely and correctly — my usual preferred approach is to set up the new 10.6 server environment, get DNS configured and operating first and only then enable the other necessary services (proper DNS is vital to a stable environment, and incorrect DNS is the trigger for more than a few weird problems with OS X Server), and then migrate over the web files from a backup. That's the most effort, but generates the "cleanest" environment.
Less preferred, but can work: using an external backup of the old OS X Server environment and migrating that data over during the installation of 10.6 is another option, but that can sometimes migrate in the old problems.

Sap service fails after switching to the second node in HA system.

Hello all,
We have installed the HA mscs cluster installation for ECC6.0(my SAP erp 2005) system.The ASCS+SCS isntance and the DB instance are the failover resources.
When the ASCS+SCS(sap cluster group) fail over to the next node the service sap_<sid>_00 (ascs) and sap_<sid>_01(scs) fails to start automatically and we have to manually start the instance from the services console by giving the sapservice<sid> password to start the services.
when we try to start the service without giving the password then the system gives a message unable to start due to logon failure and after giving the password it shows that the user has been been granted to logon as a service user.
Pl help resolve this issue.
thx
satyajit

A change to the zpool_import() management of the zpool.cache file, as delivered by Solaris 10 kernel patches 137137-09 (for SPARC) or 137138-09 (for x86), might cause systems that have their shared ZFS (zfs(1M)) storage pools under the control of HAStoragePlus to be simultaneously imported on multiple cluster nodes. Importing a ZFS storage pool on multiple cluster nodes will result in pool corruption, which might cause data integrity issues or cause a cluster node to panic.
To avoid this problem, install Solaris 10 patch 139579-02 (for SPARC) or 139580-02 (for x86) immediately after you install 137137-09 or 137138-09 but before you reboot the cluster nodes.
Alternatively, only on the Solaris 10 5/08 OS, remove the affected patch before any ZFS pools are simultaneously imported to multiple cluster nodes. You cannot remove patch 137137-09 or 137138-09 from the Solaris 10 10/08 OS, because these patches are preinstalled on that release.

XP workstation services fail after 4.90 SP2 client imports

Testing for a migration from ZFD 3.2 to ZDM 6.5 on the workstation with the new Novell
Client 4.90 SP2.
Our core XP SP1 ghost image (not OEM) restores to a Compaq D530 without issue and has
Novell Client 4.83 SP2 with the ZFD 3.2 SP2 components (WM, RM and NAL NT services)
installed on it. Allow sysprep and the post-driver and services to run and install.
Reboot.
Login to eDirectory and install Novell Client 4.90 SP2 with NetIdentity 1.2.2 and ZFD 3.2
SP3 components (WM and RM, ZFD server is still ZFD 3.2 SP2). Reboot. Workstation is
quick and stable, logs in fine with 4.90 SP2.
Reboot again. Workstation initially appears to come up quickly then right around the time
NWGINA pops up services start to drag/fail and it'll take several minutes to get to the
point to actually enter my username and password. The enhanced GINA in SP2 detects
networking has failed and checks Workstation Only automatically. Eventually get in
Workstation Only. While the Explorer shell is responsive and appears stable, most
services have failed or are hung in the process of starting.
Stripping a box in this state of the most of its apps will bring it back close to its
original speed, but you're left with networking and in particular the TCP/IP Protocol
Driver "corrupt". As repair is not an option, I'm not aware of a way to remove and/or
reinstall TCP/IP.
I've tried Option^Explicit Software's WinSock XP Fix with no success.
Breaking down our ACU install of 4.90 SP2 into parts and testing points back to the
reinstall of Workstation Manager as the initiator.
Back-revving wm.exe, wmcchlpr.dll and wmpm.dll in the 4.90 SP2 install to the 4.83 SP2
(ZFD 3.2 SP2) level does not resolve.
I have a feeling that is has something to do with after the WM components registering with
the workstation and certain policies associating and coming down. But only three are
available at "Scheduler Service Startup". NAL Workstation Association Agent, NT Client
Configuration and Windows Group Policy. The Group policy is quite small and doesn't
affect system-level stuff.
Haven't yet tried toggling them off and see what affect disabling them has.
Aside from opening a service request, any idea or anywhere else I should be looking or
testing?
Ironically, I have the 4.90 SP2 client working without issue in this setup using HP's OEM
image for the D530.
Tony Pedretti
TransUnion LLC

A combination of recreating the ZENworks Group Policies using a Windows 2000 box for
reasons described in the previous posted TID and restoring wmgrppol.dll back to the build
shipped in 4.90 SP2 (3/4/2004) prevents the issue from reocurring.
I originally back-revved wmgrppol.dll to a test build (8/7/2002) Novell sent me prior to
4.83 SP2 to work around an issue where local policies are being removed after restarting a
workstation...
Local Group Policies are removed after updating to client updates in ZfD32SP1Client.exe
http://support.novell.com/cgi-bin/se...?/10079392.htm
Looks like I can't have my Group Policies and ZENworks working too. That is until I move
to 6.5. I hope.
Tony Pedretti
TransUnion LLC

Cannot get mail, connection to the service failed after iOS7

After upgrading to iOS7, I am getting repeated "Cannot Get Mail: The connection to the server failed." message everytime I open the email. I click OK and after it goes away, I do get email later. But it happens everytime now. Reset the iPad but still happening. Do I have to hard reset the darn thing? Any ideas?

Don't hard reset.
Instead, go to Settings/Mail, Contacts, Calendars and the to Accounts. Note the settings for your iPad, then delete the account - and then reenter the information. Make sure it's 100% correct.
Many, many people - myself included - had to reenter email settings after the iOS7 update.

MDM Server Window Service failed after adding server password

After adding MDM server password, MDM server window service can't start up. We have to use clix command to start the server. Is there anyway to fix window service problem?

Hi Jean,
From the version number it sounds like you're using version 5.5 SP4, right? The Console application was significantly changed in SP5 and you would no longer see the locked server icon... If you unmount the server from the Console, and re-mount it, isn't there an option on the context menu for the tree (right-click on the server node) to provide the password? Did you try "Connect to Server" or "Start Server" on this context menu?
Thanks... I don't know if I can help you with your problem, but I will try!
-Cleopatra
Message was edited by: Author - found the option on the context menu to provide the password to the server
Cleopatra Von Ludwig
Message was edited by:
Cleopatra Von Ludwig

SUP failed over manually, voice service failed after FAILOVER, started accessing old voice vlan which was removed from config

Hey guys,
I am pretty sure, my subject is kinda confusing. Sorry about that. Here is what happened.
1. 4510r with Supervisor V 1000BaseX, switched over to standby Sup, then reseated Active SUP, once reseat complete, switched again to get the reseated SUP up and running as Active SUP.
2. a simple maintenance which was supposed to cause no outage and it did not cause any outage as well.
3. however, what i did not notice was, even though the voice vlan was configured to access 2353, they were accessing vlan 453.
4. the change was made 2 weeks prior to this maintenance where voice vlans were previously accessing 453 and they were all changed to access 2353. configs were saved.
5. however, after the maintenance, the running config showed that they were acessing 2353 but when checking the mac address on the interface, it was seen accessing 453.
6. the fix was to remove the config and re add it , that fixed it.
Has anyone else experienced the issue ? What really happened there ?
software version: Version 15.0(2)SG5
#sh module
Chassis Type : WS-C4510R
Power consumed by backplane : 40 Watts
Mod Ports Card Type Model
---+-----+--------------------------------------+------------------+-----------
1 2 Supervisor V 1000BaseX (GBIC) WS-X4516
2 2 Supervisor V 1000BaseX (GBIC) WS-X4516
3 48 10/100/1000BaseT (RJ45)V, Cisco/IEEE WS-X4548-GB-RJ45V
5 48 10/100/1000BaseT (RJ45)V, Cisco/IEEE WS-X4548-GB-RJ45V
6 48 10/100/1000BaseT (RJ45)V, Cisco/IEEE WS-X4548-GB-RJ45V
7 48 10/100/1000BaseT (RJ45)V, Cisco/IEEE WS-X4548-GB-RJ45V
8 48 10/100/1000BaseT (RJ45)V, Cisco/IEEE WS-X4548-GB-RJ45V
9 48 10/100/1000BaseT (RJ45)V, Cisco/IEEE WS-X4548-GB-RJ45V

configs were saved many times prior to the maintenance. i did a " write mem ".

[solved] shadow.service load fail Verify integrity password&group file

My system Arch with KDE 5 boot OK but in log I have: "shadow.service loaded failed failed Verify integrity of password and group files"
I make upgrade KDE 4 to next 5. I now not have installed package kdebase-workspace with KDM.
KDE start with edit boot file ~/.xinitrc - in Pantheon desktop environment https://wiki.archlinux.org/index.php/Pantheon
#!/bin/sh
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
gsettings-data-convert &
xdg-user-dirs-gtk-update &
/usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1 &
/usr/lib/gnome-settings-daemon/gnome-settings-daemon &
/usr/lib/gnome-user-share/gnome-user-share &
eval $(gnome-keyring-daemon --start --components=pkcs11,secrets,ssh,gpg)
export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID GPG_AGENT_INFO SSH_AUTH_SOCK
########## exec dbus-launch gala &
# exec cerbere
# start kde 5
exec startkde
[root@arch-linux ~]# systemctl status shadow.service
● shadow.service - Verify integrity of password and group files
Loaded: loaded (/usr/lib/systemd/system/shadow.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since śro 2015-05-27 07:55:12 CEST; 4min 41s ago
Process: 285 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
Main PID: 285 (code=exited, status=2)
maj 27 07:55:11 arch-linux systemd[1]: Starting Verify integrity of password and group files...
maj 27 07:55:12 arch-linux pwck[285]: user 'kdm': directory '/var/lib/kdm' does not exist
maj 27 07:55:12 arch-linux pwck[285]: pwck: bez zmian
maj 27 07:55:12 arch-linux systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
maj 27 07:55:12 arch-linux systemd[1]: Failed to start Verify integrity of password and group files.
maj 27 07:55:12 arch-linux systemd[1]: Unit shadow.service entered failed state.
maj 27 07:55:12 arch-linux systemd[1]: shadow.service failed.
[root@arch-linux ~]# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● shadow.service loaded failed failed Verify integrity of password and group files
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Last edited by hackintosh1984pl (2015-05-27 19:18:57)

I help me this information https://bbs.archlinux.org/viewtopic.php?id=193624
Remove line with "kdm" in file: /etc/passwd and reboot and OK is now:
[root@arch-linux ~]# systemctl --failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
I make also backup: cp /etc/passwd /etc/passwd.backup

Pwck Complaining about homeless users, causing shadow.service to fail

I was looking through my journal and noticed the following error:
Jul 08 00:00:00 raspberry_pi systemd[1]: Failed to start Verify integrity of password and group files.
Checking the status of shadow.service produces this output:
~ $ sudo systemctl status -l shadow
● shadow.service - Verify integrity of password and group files
Loaded: loaded (/usr/lib/systemd/system/shadow.service; static)
Active: failed (Result: exit-code) since Tue 2014-07-08 00:00:00 PDT; 5min ago
Process: 11736 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
Main PID: 11736 (code=exited, status=2)
Jul 08 00:00:00 raspberry_pi systemd[1]: Starting Verify integrity of password and group files...
Jul 08 00:00:00 raspberry_pi pwck[11736]: user 'remote': directory '/home/remote' does not exist
Jul 08 00:00:00 raspberry_pi systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Jul 08 00:00:00 raspberry_pi systemd[1]: Failed to start Verify integrity of password and group files.
Jul 08 00:00:00 raspberry_pi systemd[1]: Unit shadow.service entered failed state.
Jul 08 00:00:01 raspberry_pi pwck[11736]: pwck: no changes
The passwd entry for this user is
~ $ cat /etc/passwd
remote:x:1001:100::/home/remote:/bin/nologin
I guess this explains why pwck is complaining and causing shadow.service to fail. However, this user was created a long time ago, explicitly without a home directory, so I am not sure why a home path is specified in the passwd file. I also feel certain that this error is relatively new.
So, using the following command I created a test user without a home directory so that I could at least see what a passwd line for a user without a home directory is supposed to look like, but to my surprise a home path was specified in the passwd file and pwck complained about the new user in the same way.
~ $ sudo useradd -M -g users -s /bin/bash testuser
~ $ cat /etc/passwd
testuser:x:1002:100::/home/testuser:/bin/bash
~ $ sudo pwck -r
user 'remote': directory '/home/remote' does not exist
user 'testuser': directory '/home/testuser' does not exist
pwck: no changes
I also created a throwaway user on my x86 notebook to see if this happens, and it does, so this does not appear to be related to the architecture.
Is there anything I could do short of creating a home directory for this user, or does this look like a bug?

Hope it's not too late to answer this.
Changing the home directory to /dev/null seems to have solved the issue for me.
Still don't know what negative effects that might have for me, but shadow.service runs normally as far as I can tell.
Edit:
Performing
userdel -r <user>
throws
userdel: /dev/null not owned by <user>, not removing
, so setting /dev/null as the home directory is relatively "safe"
Last edited by zomernifalt (2014-11-05 15:55:36)

Address list service failed to respond error on Exchange 2007 (after adding first 2013 server)

Hi,
We just installed an Exchange 2013 server within an Exchange 2007 environment.
The Exchange 2013 (CU6) server will be used to setup a hybrid connection with O365, and move mailboxes to O365.
After installing the Exchange 2013 server it isn't possible anymore to create/enable mailboxes on the Exchange 2007 server.
We end up with an error :
Mig1 TestAccount
Failed
Error:
The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error.
Exchange Management Shell command attempted:
Enable-Mailbox -Identity 'domain.be/customer/TEMP/Mig1 TestAccount' -Alias 'mig1' -Database 'Exchange2007\SG01\DB02'
When executed via EMS we receive this error :
The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error

Hi Lyncer
This error can be caused if the default Public Folder Database not being pointed to the exchange 2007 database which you are trying to create a new mailbox.
Also it can happen if System Attendant service is not running.
Troubleshooting steps:
1) Restart the System Attendant Service
2) Point the affected database to the default public folder
Follow the below steps to do that
Open EMC
Go to Organization Configuration > Mailbox.
Select the mailbox database that you want to change the default public folder database.
Right click the database and select properties
In <Mailbox Database Name> Properties, click the Client Settings tab.
Next to the Default public folder database box, click Browse.
In Select Public Folder Database, select the public folder database from the list of public folder databases, and then click OK.
Cheers!!!
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

SQL Azure sync service-- absurdly slow and fails after a few days

Hello. We have been trying to use Azure Data Sync to replicate an on-premise MSSQL database to an SQL Azure database for read-only access by a customer. This was working for a while, but stopped syncing after a couple months(12hr auto-sync schedule) with
no errors in the log. I had to re-create the sync group, but now it takes even longer than originally to try to sync, and never actually completes, as it gets interrupted by bi-weekly server restarts... It used to take a few hours to sync the new data in our
database(which is appended to daily)-- but this time it fails after 4+ days... It was unacceptably slow initially(IMO), but now it's clearly unusable. The original initialization of the data when I first set it up was less than 2 days of syncing.
It seems there is a throttle on the Azure sync service. Is this true? Would it be best to clear the SQL Azure database now and re-sync? Is there a way to pre-load the SQL Azure database with MSSQL on-premise data via a SQL backup file or something?
Please advise. Thank you.

when you re-created the sync group, does the member databases/hub database have pre-existing data?
when synching a sync group for the first time, make sure databases don't contain the same set of data, otherwise, you will run into conflicts which will completely slow down your sync...
I deleted the initial sync group because it wasn't syncing(auto or on-demand), nor creating a log entry with an error indicating why.
So, I simply deleted the sync group and re-created it with the same exact databases and settings. I did not delete all data in the SQL Azure database-- I was under the assumption that the sync service, with the tracking tables were smart enough to not get
confused with pre-existing data, but apparently that's not how this works?
I obviously can't delete the data in the source database(MSSQL on-premise), but I could delete the tables in the SQL Azure database if that's supposed to fix the problem-- then we'll just have to wait multiple days for it to be completely re-initialized,
hopefully without error... Is there a way to seed the data in some way to prevent this extremely log first sync?
Thank you for your help.

Shadow.service fails after LightDM uninstall

Similar Messages

Maybe you are looking for