No problems. My GL server and web are on different systems, I stopped both of them before the upgrade. Below is what I did for the server, use the same procedure for the web. The new server.conf is saved to /etc/graylog/server/server.conf.rpmnew
# rpm -Uvh https://packages.graylog2.org/repo/packages/graylog-1.3-repository-el7_latest.rpm Retrieving https://packages.graylog2.org/repo/packages/graylog-1.3-repository-el7_latest.rpm Preparing... ################################# [100%] Updating / installing... 1:graylog-1.3-repository-el7-1.3.0-################################# [ 50%] Cleaning up / removing... 2:graylog-1.2-repository-el7-1.2.0-################################# [100%] # yum clean all Loaded plugins: fastestmirror Repodata is over 2 weeks old. Install yum-cron? Or run: yum makecache fast Cleaning repos: base epel extras graylog updates Cleaning up everything Cleaning up list of fastest mirrors # yum -y upgrade graylog-server Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Resolving Dependencies --> Running transaction check ---> Package graylog-server.noarch 0:1.2.2-1 will be updated ---> Package graylog-server.noarch 0:1.3.0-3 will be an update --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Updating: graylog-server noarch 1.3.0-3 graylog 65 M Transaction Summary ================================================================================ Upgrade 1 Package Total download size: 65 M Downloading packages: Delta RPMs disabled because /usr/bin/applydeltarpm not installed. graylog-server-1.3.0-3.noarch.rpm | 65 MB 01:07 Running transaction check Running transaction test Transaction test succeeded Running transaction Warning: RPMDB altered outside of yum. Updating : graylog-server-1.3.0-3.noarch 1/2 warning: /etc/graylog/server/server.conf created as /etc/graylog/server/server.conf.rpmnew Cleanup : graylog-server-1.2.2-1.noarch 2/2 Verifying : graylog-server-1.3.0-3.noarch 1/2 Verifying : graylog-server-1.2.2-1.noarch 2/2 Updated: graylog-server.noarch 0:1.3.0-3 Complete! # systemctl start graylog-server # systemctl status graylog-servergraylog-server.service - Graylog server Loaded: loaded (/usr/lib/systemd/system/graylog-server.service; enabled) Active: active (running) since Tue 2015-12-15 10:08:59 PST; 7s ago Docs: http://docs.graylog.org/ Main PID: 24949 (graylog-server) CGroup: /system.slice/graylog-server.service ├─24949 /bin/sh /usr/share/graylog-server/bin/graylog-server └─24950 /usr/bin/java -Xms1g -Xmx1g -XX:NewRatio=1 -XX:PermSize=12... Dec 15 10:08:59 hilphlgrayp02.solarworldusa.net systemd[1]: Started Graylog s... Dec 15 10:08:59 hilphlgrayp02.solarworldusa.net graylog-server[24949]: OpenJD... Dec 15 10:08:59 hilphlgrayp02.solarworldusa.net graylog-server[24949]: OpenJD... Hint: Some lines were ellipsized, use -l to show in full. -Alex On Thursday, December 10, 2015 at 9:15:13 AM UTC-8, Emerson Coimbra wrote: > > Hi, > > I have a Graylog 1.2 server running on a CentOS 7. The installation is > done with yum in the official Graylog repositories. > > I would like to upgrade to 1.3, but I found no information on updating in > the official documentation and I think: > > And if I change the /etc/yum.repos.d/graylog.repo file for version, point > to version 1.3 and then run yum update - This surely will upgrade to > version 1.3, but it will have any side effects? > > I looked at the new graylog-server.conf file and there are few new > entries. Is there any major change in the core Graylog to prevent an update > over the old version? > > > Thanks, > Emerson > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/da65edef-b541-4935-bba7-1749a7cef88f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.