Unable to search in graylog - graylog

I am trying to figure why graylog displays this error in the search tab:
I tried searching the web for clues and this was the closest but it did not state the resolution: https://community.graylog.org/t/unable-to-perform-search-query-1-293-bool-unknown-field-disable-coord/16582. Could it be some misconfiguration?

Related

Issue with Microsoft EDGE and opening links in new tab. Specifically Google search results. Possibly a RendererCodeIntegrity Issue?

Video: https://www.screencast.com/t/nZr2b9KBRSf7
Opening Google Search Results in a new tab results in non functionining pages for me. However if I hit REFRESH on those problematic pages it takes me to the desired site without any issues.
The issue only appears to affect Microsoft EDGE and not Google Chrome. And the broken links seem to only be problematic when opening Google Search results in a new tab.
I reset my browser settings back to default.
I also added the following registry entry as described below for RendererCodeIntegrityEnabled:
https://browserhow.com/how-to-fix-microsoft-edge-status_access_violation/
Finally I changed the shortcut of EDGE to disabled the rendered cod eintegrity as well:
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" – disable-features=RendererCodeIntegrity
...
On the problematic pages, the parameters in the URL look like the following:
https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwiYu8Th97
url: 'sa=t'
rct: 'j'
q: [null]
esrc: 's'
source: 'web'
cd: [null]
This resolved itself after a Windows Update. Weird bug...

Unable to access Influxdb web UI. It shows 404 page not found error

I have my influxdb working in server. When I try to open the influxdb UI using http://my_host:8086. I'm receiving 404 as response. What am I missing ? help me with this please.
In version 1.3, the web admin interface is no longer available in InfluxDB. The interface does not run on port 8083 and InfluxDB ignores the [admin] section in the configuration file if that section is present. Chronograf replaces the web admin interface with improved tooling for querying data, writing data, and database management. See Chronograf’s transition guide for more information.
enter link description here

No log information for the Starting Neo4j failed... issue

I get the following error when trying to restart neo4j after adding a new procedure in the plugin folder:
Starting Neo4j failed: Component
'org.neo4j.server.database.LifecycleManagingDatabase#1d15704a' was
successfully initialized, but failed to start. Please see attached
cause exception.
My problem is not it failing to start (which i know is due to a flaw in my procedure plugin) but the lack of logs or messages suggesting what the issue may be.
It seems other people get some sort of error message: https://github.com/jbarrasa/neosemantics/issues/14
I have found two logs:
%appdata%\Neo4j Community Edition\logs
2017-05-25 09:20:03.840+0000 INFO [o.n.s.CommunityNeoServer] ========
Neo4j 3.1.3 ======== 2017-05-25 09:20:03.860+0000 INFO
[o.n.s.d.LifecycleManagingDatabase] Starting... 2017-05-25
09:20:04.678+0000 INFO [o.n.b.v.r.WorkerFactory] Bolt enabled on
localhost:7687.
..Documents\Neo4j\default.graphdb\logs
I wont paste this log unless requested as its long but there is only INFO lines and none of it looks interesting.
So is there anyway to turn logging on or am i missing a log that has info?
Developing will become a nightmare if every error forces me to keep manually testing each small change until i find the problem.
See neo4j.com/blog/user-defined-functions-neo4j-procedure-compil‌​er also grep the logs on your package name, its easy to miss a needle in a hay stack

Large amount of 404 Not Found errors due to unknown reason

My website worked correctly until last week, when suddenly lots of "not found" errors appeared. The error message is visible but I cannot find the reason. The errors stated that the pages that are unable to be found are linked from sitemap.xml, however prior to the errors appearing Google was able to crawl through the website correctly. Here is an example:
Real link in sitemap (This is the old link that is still functional):
https://rohamweb.com/webdesign/174-طراحی-حرفه-ای-سایت-در-تهران.html
What the search console is actually pointing to:
https://rohamweb.com/webdesign/174-
Apparently the crawlers cannot read content after -, likely due to the different language. I have never encountered this issue until last week, in which perviously was functional.
Thanks in advance for the help!
If this is the actual link :https://rohamweb.com/webdesign/174-طراحی-حرفه-ای-سایت-در-تهران.html, you are doing it wrong and it should be URL encoded before sending it to the response:
https://rohamweb.com/webdesign/174-%D8%B7%D8%B1%D8%A7%D8%AD%DB%8C-%D8%AD%D8%B1%D9%81%D9%87-%D8%A7%DB%8C-%D8%B3%D8%A7%DB%8C%D8%AA-%D8%AF%D8%B1-%D8%AA%D9%87%D8%B1%D8%A7%D9%86.html
In this case, all of the available engines are able to follow it.

MODx Parse Error on home page

I've been having this error over lot of modx evolution 1.0.5 installations (I allways use 1&1 servers, in Linux version) It fails to load the home page (not any other pages) it seems that every time I clean the cache, via the manager or via API code, it creates again this file in the cache:
docid_1.pageCache.php
But the thing is that even if the folder cache and all the files inside are set to 777 permissions when it creates files for caching they have any permission set and that's the thing causing this error.
Anybody has had this error? I've been searching in MODX forums but didn't find anybody worried about this, but still I can see it's something happening a lot since when I search on google this error, I don't find forum posts discussing this but instead lots of modx frontend pages showing this error at their home pages.
Maybe it's a problem with 1&1 PHP configuration.
I'm really worried about this cose it has happen some times when I client calls me "über mad" complaining about his home page showing this error.
I've seen that new 1.06 version has some fix on the pagecache parser but I don't know if it's related to my problem.
Here's the error page:
« MODx Parse Error »
MODx encountered the following error while attempting to parse the
requested resource: « PHP Parse Error »
PHP error debug Error: file(assets/cache/docid_1.pageCache.php) [function.file]: failed to open stream: Permission denied
Error type/ Nr.: Warning - 2
File: /homepages/3/d405318697/htdocs/t3st/manager/includes/document.parser.class.inc.php
Line: 413
Line 413 source: $flContent= implode("", file($cacheFile));
The cheeky answer? - "upgrade" Evolution is dead.
A more helpful answer, check the modx system settings, in Revolution you can tell modx what permissions to attempt to set on files, my guess is that maybe you have inadvertently set these to 000 if that's what you mean by this: "they have any permission set"
If that does not work/you get desperate, disable all caching and test or if possible [still not familiar with evo] set that resource to not be cached.
Though something odd is going on, please confirm; the index page will be cached but with no permissions i.e. 000, subsequent pages will be cached but do have correct permissions set? i.e. 666 [or 644/whatever]

Resources