- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2022 03:17 PM
I just installed a midserver for my developer instance to play around with creating discovery patterns but I can't get it to validate. It is installed on Linux (Debian) and the user I am using has sudo access but I'm thinking that may not be right or maybe that isn't enough?
Solved! Go to Solution.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2022 09:10 PM
see if this KB helps.
MID Servers stuck in validating state
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0727757
Regards
RP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2022 08:59 AM
I've updated the user to have the same uid and gid as root and now it is no longer validating. But how would this help? Root users don't have ssh access. So now that it is root, it can't be used as a credential. So I need to create another user that can log into all of my servers and workstations?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2022 01:11 PM
1. You must use a normal linux user to set up the mid server.
2. After mid server is created in your ServiceNow instance and Validated status is Validating, on the Linux server, open /etc/passwd and change the uid and gid of the midserver user to the same as root (usually 0).
3. Restart the midserver. Validated will now show Yes.
However, you likely won't be able to connect with this account because most Linux servers don't allow or suggest against allowing a root user to use ssh.