- CheckMates
- :
- Products
- :
- Quantum
- :
- Management
- :
- Re: Cant start API or log into web UI after import...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Cant start API or log into web UI after importing Azure cp mgmt server config
Hey guys,
Hope someone might be able to guide me in right direction here. So, here is the scenario.
Customer has had Azure CP mgmt server for few years, which has only about 20 rules or so and they now want to move all that over (integrate if you will), with S1C instance.
I build R81.20 jumbo 96 mgmt lab, imported their config after running migrate server, all went well, rebooted, but realized that as soon as that was done, Apache would not start, hence api is is failing and even web UI does not load.
I tried changing the port, rebooting, changing NIC type, no joy. Also tried below sk, but all I get is this:
https://support.checkpoint.com/results/sk/sk169656
UEPM: Starting Apache...
/opt/CPuepm-R81.20/engine/scripts/uepm_functions: line 70: /opt/CPuepm-R81.20/logs/uepm/uepm_stop_start.log: No such file or directory
grep: to: No such file or directory
grep: find: No such file or directory
grep: the: No such file or directory
grep: value: No such file or directory
UEPM: Apache Web Server is starting...
/opt/CPuepm-R81.20/engine/scripts/uepm_functions: line 70: /opt/CPuepm-R81.20/logs/uepm/uepm_stop_start.log: No such file or directory
UEPM: WARNING - Failed to start Apache Web Server
/opt/CPuepm-R81.20/engine/scripts/uepm_functions: line 70: /opt/CPuepm-R81.20/logs/uepm/uepm_stop_start.log: No such file or directory
If anyone has an idea, happy to try.
Thanks so much as always!
Andy
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I fixed the issue by copying httpd2.conf file from /web/conf dir in customer's mgmt to my lab and once api restart command was done, all worked fine.
Cheers,
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Curious why uepm is involved here (Endpoint Management).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Weird, dont see it in their environment either...
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
FWIW, when I ran cpwd_admin list in my lab, I noticed 3 processes for log exporter as down, so removed them all, rebooted, now all shows E and 1, but apache still down...
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did the original server have Endpoint policy management enabled? Looks like this new VM is looking for the Endpoint management pieces from the migrate import, but they're not installed. Did you do the Gaia First Time Wizard via the initial install WebUI, via config_system, or through the Azure Marketplace setup? Again, looks like one of those didn't get the correct product selection for installation.
This is bit of a stupid question, but: Did you run the Gaia First Time Wizard yet, before running migrate_server import? 🙂
The multiple "grep" command errors are also interesting. That's a series of sequential words that is likely from an improperly defined (or missing) Bash variable resulting in that kind of erroneous output. The error sequence in question is in the "start_apache()" function of the "uepm_functions" shell library. However, the expected UEPM log file doesn't exist, likely because the paths don't exist, again, because the UEPM product isn't installed/configured.
You're also using HFA 96 which is rather bleeding edge. I'd suggest re-doing this VM with HFA 92 instead, "just because".
Hope some of this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oh, and another possibly stupid question: Is the IP of this new VM the same as the IP of the original, for the license to be activated?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey Duane,
Totally different IP and yes, I 100% made sure license was indeed correct.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Glad you mentioned licences, since it made me realize we need to verify what they are currently using. Im fairly sure when it comes to VMSS infrastructure, it all has to be centrallly licenced.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yeah VMSS has to use vsec_lic_cli just as all CloudGuard licenses, plus you need to use CME to bootstrap those scale-out instances, and torch the scale-in ones when that time comes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think thats what we may need to do once converted.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I fixed the issue by copying httpd2.conf file from /web/conf dir in customer's mgmt to my lab and once api restart command was done, all worked fine.
Cheers,
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If that's the case, then sounds like the default web port was changed on the original server. That's in CLISH ("show web ssl-port"). I'd be concerned if this happens again on the next reboot, tho. That httpd.conf file is generated dynamically by /bin/httpd_xlate and based on the contents of the CONFD configuration. I say reboot that server and make sure it comes back up correctly! 🤞
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Im glad I was able to fix it by copying the file I mentioned, but nothing was changed on original server Duane. That environment has been around for 4 years now and I could literally count number of changes done to it on both hands.
Cheers,
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Also something else I wanted to mention, in case anyone else has this issue 🙂
So, when I copied httpd2.conf from working mgmt to lab, it all worked after doing api restart, but after reboot, it did NOT work, so had to run chattr +i httpd2.conf command, then rebooted again, now apache shows started as below and all still works fine.
Thanks guys!
Andy
API Settings:
---------------------
Accessibility: Require all granted
Automatic Start: Enabled
Processes:
Name State PID More Information
-------------------------------------------------
API Started 5952
CPM Started 5952 Check Point Security Management Server is running and ready
FWM Started 5509
APACHE Started 4354
Port Details:
-------------------
JETTY Internal Port: 53910
JETTY Documentation Internal Port: 53314
APACHE Gaia Port: 443
Profile:
-------------------
Machine profile: Large SMC env resources profile without SME
CPM heap size: 1280m
Apache port retrieved from: dbget http:ssl_port
--------------------------------------------
Overall API Status: Started
--------------------------------------------
API readiness test SUCCESSFUL. The server is up and ready to receive connections
Notes:
------------
To collect troubleshooting data, please run 'api status -s <comment>'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hmm that's concerning. You shouldn't have to chattr +i the httpd config. Seems like something is amiss in the CONFD (clish) config, or.... you have a Jumbo HFA 96 bug. Can you remove that and try JHF 92 instead to compare?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would usually try that just for my own testing, but since its such a small ruleset, wont bother, since lab is functional now. I just want to have lab "alive", until we do the full cutover 🙂
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Compare content of "working" httpd2.conf with not working using linux "diff" command and lets see what is difference.
Jozko Mrkvicka
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Great idea, but I already replaced the file. Im sure difference was significant, since original was 1K in size and one I copied from client's azure mgmt was 21K.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I recall CP PS guy did work for Azure vmss back in the day, though whole idea was to eventually use it for vpn/remote access, which was supported back in 2021, but I think it was not some time in 2022, so thats the reason why they wish to integrate all this with S1C now.
Andy
