Closed oluoo closed 1 year ago
Hey @oluoo,
thanks for reporting this. Just to make sure: You are mentioning that you are upgrading to v5.1.2
, but the plugins you are listing are all 5.0.8
. Is this on purpose?
@dennisoelkers thanks for your response. Yes I did upgrade using the steps provided and the 5.0.8v
plugins were installed by default alongside the upgrade of Graylog. Are the versions for the plugins expected to be different?
For what its worth, i believe @BlueTeamNinja ran into this about a month ago and reported back with:
Not specifying the plugin dir caused this startup failure.
@oluoo can you share/verify what your graylog server config file (server.conf
) has for plugin_dir
?
Example: plugin_dir = /usr/share/graylog-server/plugin
That is absolutely how the error presented. Either Graylog doesn't have permission to read the plugin dir, or in this case, I would venture the plugin directory was pointed somewhere different (conf or container variable/volume) to include the additional plugin and is now missing the original required plugins.
That's my guess in this situation. Let us know if this helps you resolve this issue.
Cheers.
@drewmiranda-gl & @BlueTeamNinja , as requested, here a the config line for the plugin_dir
#Set plugin directory here (relative or absolute)
plugin_dir = /usr/share/graylog-server/plugin
The metrics-reporter-prometheus plugin that was added initially had been removed, and the plugin list restored to default plugin.
The plugin versions should all be the same version as the Graylog version itself, if there are 5.0.8 plugins in there, those will not work. Maybe there is a mistake in the upgrade docs? Can you point to which instructions you followed so we can check, please?
Sure, @kroepke - here is a link to the list of upgrade instructions.
I will review the plugin lists, and update it accordingly if necessary
Can you also double check the permissions?
What is the result of ls -lah
in your plugin directory?
Get Outlook for Androidhttps://aka.ms/AAb9ysg
From: olu @.> Sent: Monday, July 10, 2023 3:12:38 PM To: Graylog2/graylog2-server @.> Cc: Abe @.>; Mention @.> Subject: Re: [Graylog2/graylog2-server] Graylog does not start after upgrade from 4.2.9-1 to 5.1.2-1 (Issue #15854)
Sure, @kroepkehttps://github.com/kroepke - here is a link to the list of upgrade instructions.
I will review the plugin lists, and update it accordingly if necessary
— Reply to this email directly, view it on GitHubhttps://github.com/Graylog2/graylog2-server/issues/15854#issuecomment-1629568405, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAONW35T2F4HDHQZZJWFNOLXPRH2NANCNFSM6AAAAAAZ2IDYBM. You are receiving this because you were mentioned.Message ID: @.***>
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.
While on version 4.2, I imported in the metrics-reporter-prometheus plugin and restarted the service, and came by the Guice Error. In a bid to resolve, I cleaned out the plugin, shut down all services, and upgraded all components include Graylog Service to the respective compatible versions.
Right now, Graylog restarts every other second, but gets killed.
Expected Behavior
Graylog service should run. All other components, MongoDB & Elastic Search are all running.
Current Behavior
Right now, Graylog restarts every other second, but gets killed. Here is the logs from the /var/log/graylog-server/server.log
Plugin List
v4.2.9
v.5.1
Your Environment