› Forums › OCP Community Discussion Forum › New Realm and Jobs
- This topic has 3 replies, 2 voices, and was last updated 1 year, 3 months ago by codingadvocate.
December 13, 2021 at 5:32 pm #537G25Participant
I’m sharing this just to know if this is a bug or just misconfiguration on the creation of a new Realm (Mexico) and Jobs (related to this new realm in order to separate the environments). So I get to create a new Realm (and copied all the “OS_Parameters”/”Default Config” from default Realm) and add some networks to test with duplicate jobs for this Realm and when I duplicate all of the jobs under “findEndpoints” there are 2 of them that don’t work (the rest of the jobs are working fine and discovering assets) but I’m getting weird error message with the “find_Powershell” and “find_SSH”.
If I check the “contentGatheringService.log” I get this error with that jobs:
Exception with updating job ‘findEndpoints.find_PowerShell_MX’: [‘Traceback (most recent call last):\n’, ‘ File “C:\\Software\\openContentPlatform\\framework\\service\\networkService.py”, line 562, in getJobUpdates\n self.scheduler.remove_job(self.activeJobs[jobName])\n’, ‘ File “C:\\Users\\AdminCMDB\\AppData\\Roaming\\Python\\Python39\\site-packages\\apscheduler\\schedulers\\base.py”, line 626, in remove_job\n raise JobLookupError(job_id)\n’, “apscheduler.jobstores.base.JobLookupError: ‘No job by the id of 14 was found’\n”]
The only thing I changed on the duplicate job “find_Powershell” are the “realm”, “clientGroup” and “credentialGroup” values as the same as the other jobs, but with the Powershell/SSH can’t make it work.
Is this a bug or maybe I’m doing something wrong?
December 14, 2021 at 10:37 pm #539codingadvocateParticipant
Are you saving the copied jobs with different names? Jobs need unique names within the same package (e.g. within findEndpoints).
December 16, 2021 at 6:33 pm #540G25Participant
Yes, I’ll try to explain better, when I duplicate a job I change both the unique name and the realm:
But for example, not all jobs are working with this configuration. If I duplicate and change the name and the realm of this jobs:
find_ICMP_socket_weekly_MX -> Works
find_SNMP_MX -> Works
find_WMI_MX -> Works
find_PowerShell_MX -> Not working
find_SSH_MX -> Not working
I get this error on the “find_PowerShell_MX” but the strange things is I don’t have “Config groups” for the default realm either.
2021-12-15 10:40:20.111315 info Prepare job: ‘findEndpoints.find_PowerShell_MX’
2021-12-15 10:40:20.123316 error loadPlatformSettings: No entry found in table “class ‘database.schema.platformSchema.ConfigGroups'” for realm ‘Mexico’
December 16, 2021 at 6:39 pm #542codingadvocateParticipant
If you look at the database level, you’ll see you have a few entries on the default realm (even if empty) that need to exist for any new realm. You can create those in the Admin Console, on the DB level, or via the API. But those are: OS Parameters, Config Groups, and Default Config.
And the reason you’re only hitting an error on the shell jobs, is because those are the ones that use those configs. You can see this in the job parameters too, with “loadConfigGroups” being set to true. Happy discovery! 😉
- You must be logged in to reply to this topic.