i encountered a problem while working with the NetworkManager service on my Raspberry pi 4, i am running it with openSUSE Tumbeweed JeOS, so the default is not networkmanager but wicked, i started to notice that every time i tried to restart it the service failed.
Watching through the logs i noticed this:
Oct 31 16:49:37 suse-server NetworkManager[2966]: <warn> [1635698977.7227] config: Default config file invalid: /etc/NetworkManager/NetworkManager.conf: Key file contains line “404: Not Found” which is not a key-value pair, group, or comment
Basically every time NetworkManager is restarted something overwrites the config file, probably with a predefined template from GitHub (when you open a invalid link in raw.github.com you get 404: Not Found), i temporarily switched back to wicked but i need to resolve this problem because i need to run HASS.IO, which unfortunately supports only NetworkManager.
Related
I just installed a new WebSphere 8.5.5 ESB on Linux Centos 7.
All installation i did with root user.
Than i did the following steps to create a Web Service:
1) create server with user wasadmin
2) Generate plugin
3) Propagate plugin
In the last step i get the error:
PLGC0049E: The propagation of the plug-in configuration file failed for the Web server. test2lsoa01-02Node01Cell.XXXXXXXXX-node.IHSWebserver.
Error A problem was encountered transferring the designated file. Make sure the file exists and has correct access permissions.
The file /u01/apps/IBM/WebSphere/profiles/ApplicationServerProfile1/config/cells/test2lsoa01-02Node01Cell/nodes/XXXXX-node/servers/IHSWebserver/plugin-cfg.xml exist.
I gave him for test chmod 777 plugin-cfg.xml
Still the error is not going away.
Can someone help?
User wsadmin would be the user attempting to move the file. Ensure that ID can access /u01/apps/IBM/WebSphere/profiles/ApplicationServerProfile1/config/cells/test2lsoa01-02Node01Cell/nodes/XXXXX-node/servers/IHSWebserver/plugin-cfg.xml and there should be a target directory as well (in the webserver installation where plugin-cfg.xml is being moved to). Ensure that wsadmin has write access to this target location if propagating using node sync. If using IHS admin, ensure that the userid/password defined in the web server definition has write access to the target location.
A good test would be to access the source plugin-cfg.xml using wsadmin userid and attempt to manually move the file to the target location with the appropriate ID (based upon use of node sync or IHS admin).
Is there any log rotation in Vora 1.3? After 2 months of running Vora 1.3 I realized I'm almost of disk space on my nodes because /var/log/vora-manager is like 46 Gb. So I had to stop it, kill the logs and restart.
But maybe I missed some setting?
Edit 1: The log file is supposed to be stored in /var/log/vora/vora-manager, not the folder I mentioned above, but still I saw a huge log file there. The file /var/log/vora-manager is also mentioned in the line 178 of control.py script that is supposed to start a worked vora-manager.
You are right -- the vora-manager log file is not written into the standard /var/log/vora directory, instead it is written to /var/log/vora-manager. This has been corrected in Vora 1.4.
The logs should be rotating based on the vora_manager_log_max_file_size variable which is also set in Ambari.
Something must have gone wrong whenever vora tries to rotate the logs. I propose you search through your log file for the following line and see if it is followed by some kind of error:
vora.vora-manager-master: [c.740b0d26] : Running['sudo', '-i', '-u',
'root', '/usr/sbin/logrotate', '/etc/logrotate.d/vora-manager-master']
You can also change the verbosity of the logger by setting the vora_manager_log_level config variable in Ambari from INFO to WARNING. Be ware this will hide the log rotation log messages.
When I click on publish, it says initializing and the process goes on. It happens with both publish item or publish site (Smart publish).
Using Sitecore 8.2. The instance is in the local PC and the DB is the remote server. There is no issue when creating a new item.
I checked the logs. There are two files with the name "log". Is this normal.
The first log file has the below error:
ManagedPoolThread #16 14:12:45 ERROR Unable to connect to server
localhost:27017: No connection could be made because the target
machine actively refused it 127.0.0.1:27017.
The second one has this:
12488 14:13:18 ERROR Exception when executing agent
aggregation/automationRangeManager Exception:
System.NullReferenceException Message: Object reference not set to an
instance of an object. Source: Sitecore.Analytics.MongoDB at
Sitecore.Analytics.RangeScheduler.MongoDbRangeMap2.GetRightKey() at
Sitecore.Analytics.Automation.Aggregation.Data.Processing.RangeManagerAgent.Execute()
at Sitecore.Analytics.Core.BackgroundService.Run()
I do not have MongoDB installed in the local PC or in the remote DB server, because, this is not needed for this project.
This worked for me:
Go to Website\App_Config\Include
Open Sitecore.Xdb.config
Set Xdb.Enabled to false and Xdb.Tracking.Enabled to false.
I have a particular scheduled task that CF claims runs every 2 minutes. However, it either doesn't run or complete since the database changes the task is supposed to perform do not occur after each run. However if I copy the exact same URL into a browser and run the script, it works 100% of the time.
I have no clue where to start debugging. There is no IP restriction on the page.
I can see in the CF Admin that it was last run at 2:06 for example and the next run will be at 2:08. I can also see it in the scheduler.log file.
We had updated our certs in IIS but didn't update our cacerts file. Once we did everything was great.
It was clear the process wasn't running when I added a line or two to email myself at the start of the task. The emails never came when the server ran the task but they did when I pinged the page. I changed the task to save the output to a log file and when I opened that up it just said "Connection Failure". This led me to some googling and some talk about certificates which made me remember that we just updated ours recently. Looking back at my emails with IT it did indeed happen on the same day that the last emails in the mailsent.log were sent from these scheduled tasks.
I have downloaded the elb packarge from the AWS site and set the required environment variables but I am unable to use the commands.
Can anyone tell me why I am getting this error:
elb-describe-lbs --aws-credential-file /home/prateek/credential-file-path.template
elb-describe-lbs: Refused: Signature not yet current: 20131118T182313Z is still later than
20131118T125753Z (20131118T125253Z + 5 min.)
AWSRequestId:56c9101b-5050-11e3-9f02-ff424c27b77f
It appears that your system time is off. Most api tools require your system time to be within 5 minutes of the current time. Its one of the elements used to verify the validity of the request.