mcpd err - current folder has been removed
Hello Everyone, Anyone encountered the below mcpd errors after removing a user account? they have been appearing frequently ever after. err mcpd[4311]: 01070734:3: Configuration error: Current folder has been removed. Exit session. err mcpd[4311]: 01070827:3: User login disallowed: User (dummy-user) is not an administrator, does not have a UID of zero, and has not been assigned a role on a partition.
Web interface showing "Starting web server" and CLI shows "logger: Re-starting mcpd" every 2 seconds after shutting down 13.1.0.5 Build 0.0.5 Virtual
I have an F5 LTM virtual machine loaded up on a GNS3 VM for a lab. The virtual machine is activated with interfaces/VLANs and a couple pools/VIPs and a policy. When I go to shut down the virtual, I am greeted with the web interface saying... Starting web server Please do not reboot your device. The device is starting services required for the communication with the configuration utility. This process takes approximately 1-2 minutes. and then it runs for 30+ minutes. Logging in to the console with the root account results in endless logger: Re-starting mcpd I have tried... touch /service/mcpd/forceload Forcing a file system check on the next system reboot I should also note that the CLI shows that the LTM is INOPERATIVE so I cannot issue TMSH commands. This issue has happened to me earlier in the week and I just decided to install it as a new VM but I do not want to have to do that every time I need to shut down my host. The lab is only temporary and for testing so I just need to make sure things work but I do not want to have to keep the virtual machine running when I am done for the day in order to keep this machine working. I should also mention this is just a trial license. Any help would be much appreciated.MCPd Heartbeat
All, Currently running into a bug where we have too many objects and a work around provided was to disable the MCPD heartbeat between our LTMs. Can someone give me a deep dive into the MCPD process and the pros/cons of disabling the heartbeat that people have experienced from a real world perspective? Please advise and thank you, Dan
BIG-IQ 7.1.0 on AWS - MCPD issues
I have previously been running BIG-IQ v6 in AWS without issues. Last week I deployed BIG-IQ v7.1.0 however I keep having the following issue; after I reboot the instance, the mcpd service is reported as not running or keeps restarting. WebGUI does not even load, and SSH sometimes returns a slow/unresponsive tmsh session, and other times errors out and closes the session. Steps to re-create: Deploy BIG-IQ v7.1.0 from the AWS Market place Allocate Elastic IP, Start Instance and Add a Trial License Add a new device (BIG-IP running 12.1.5.2) Deploy AS3 declarations to the BIG-IP Delete the AS3 declared applications (through AS3) Shutdown the instance from tmsh Start the instance Issues Observed: The Web GUI does not load Attempts to SSH to the BIG-IQ return an error : cfg exception: (The connection to mcpd has been lost, try again.) Viewing the system log from AWS Console shows multiple entries of 'Starting Retrieve public keys for ssh(aws-init): runsvstat: warning: /service/restnoded: runsv not running. runsvstat: warning: /service/restnoded: runsv not running. I would like to know : Is this a known issue? Is there a known cause? I could not find any KB articles that relate to this. How can one recover the BIG-IQ since neither GUI nor SSH are operational?How does the mcp daemon work together with bigip.conf, mcpdb.bin and the running configuration?
Hey guys! The background to this question is the scenario for when the binary configuration (mcpdb.bin) and the text configuration (bigip.conf) gets out of sync. The scenario and soloution is presented in the following SOL13030: Forcing the mcpd process to reload the BIG-IP configuration According to the SOL article, from BIG-IP version 9.4.0 and onwards, mcpd process loads the text configuration files (bigip.conf and bigip_base.conf) into the running configuration during the first boot up and builds a binary configuration image. These are created into the two files: /var/db/mcpdb.bin /var/db/mcpdb.info It does this in order to faster load the configuration without needing to parse and validate the configuration. As the above statement says, the mcpd process builds the binary configuration image during first boot but how does it work after the first bootup? When you make a configuration change using the WebGUI, does the BIG-IP system save configuration to the running configuration, text configuration AND the binary configuration? How can a mismatch between the binary and the text configuration occur in the first place? In our case there are configuration from over a month ago that is mismatching. The binary configuration complains that objects are missing that was removed over a month ago that is not present in the bigip.conf file. What causes such a long delay of the configuration mismatch? Thanks!
Lost GUI access to BIG IP 4000
We have a new pair of Big IP 4000 with version 11.6.0.Majority of the initial configuration has been completed. We have lost access to the GUI on the standby device and it is showing as disconnected on the primary/active device group. we are able to ping the standby device. logging into the cli shows the following continuous output. Sep 28 11:44:44 emerg logger: Re-starting lind Sep 28 11:44:44 emerg logger: Re-starting mcpd Sep 28 11:44:45 emerg logger: Re-starting lind Sep 28 11:44:46 emerg logger: Re-starting mcpd How can we get back the device into operational state?
