Yeah, I span up a fresh copy in a VM and it was perfectly fine.  MD5'd the 
gpg and sources files between the broken servers and good VM.  Identical. 
 Removed the gpg and sources files, ran an apt-get update, put them back in 
place (same md5sums again), re-ran the apt-get update and all is well. 
 It's possible an apt-get clean may have also achieved the same thing. 
 Very weird.

P.

On Friday, November 6, 2015 at 10:30:32 PM UTC+13, Bernd Ahlers wrote:
>
> Patrick, 
>
> I am unable to reproduce this on a fresh Ubuntu 14.04. I have been using 
> the repo package to setup the repository. 
>
>
> https://packages.graylog2.org/repo/packages/graylog-1.2-repository-ubuntu14.04_latest.deb
>  
>
> Maybe "apt-get clean ; apt-get update" helps? 
>
> Regards, 
>         Bernd 
>
> Patrick Brennan [Thu, Nov 05, 2015 at 02:25:13PM -0800] wrote: 
> >Hi there, 
> > 
> > 
> >I am seeing apt key errors when trying to update to 1.2.2: 
> > 
> ># apt-get update 
> >[ . . . SNIP . . .] 
> >Fetched 473 B in 7s (65 B/s)                                             
>   
> >     
> >Reading package lists... Done 
> >W: GPG error: https://packages.graylog2.org trusty Release: The 
> following 
> >signatures were invalid: BADSIG D44C1D8DB1606F22 TORCH GmbH 
> ><[email protected]> 
> > 
> > 
> > 
> >The key is definitely in the keyring: 
> > 
> ># apt-key finger 
> >[ . . . SNIP . . .] 
> > 
> >/etc/apt/trusted.gpg.d/graylog2-keyring.gpg 
> >------------------------------------------- 
> >pub   2048R/B1606F22 2014-06-04 
> >      Key fingerprint = 28AB 6EB5 7277 9C2A D196  BE22 D44C 1D8D B160 
> 6F22 
> >uid                  TORCH GmbH <[email protected]> 
> >[ . . . SNIP . . .] 
> > 
> > 
> > 
> >And it appears to match the version currently specified in the 
> repository: 
> > 
> ># wget https://packages.graylog2.org/repo/debian/keyring.gpg 
> ># md5sum keyring.gpg graylog2-keyring.gpg 
> >a2f5c4745035bb3f401c1b0605011761  keyring.gpg 
> >a2f5c4745035bb3f401c1b0605011761  graylog2-keyring.gpg 
> > 
> > 
> > 
> > 
> >There have been no configuration changes on the servers since the initial 
> >installation.  Any suggestions appreciated! 
> > 
> >Thanks, 
> >Patrick 
> > 
> >-- 
> >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 [email protected] <javascript:>. 
> >To view this discussion on the web visit 
> https://groups.google.com/d/msgid/graylog2/8e52fc9a-dece-4f34-b19d-402444b9bff4%40googlegroups.com.
>  
>
> >For more options, visit https://groups.google.com/d/optout. 
>
>
> -- 
> Developer 
>
> Tel.: +49 (0)40 609 452 077 
> Fax.: +49 (0)40 609 452 078 
>
> TORCH GmbH - A Graylog company 
> Steckelhörn 11 
> 20457 Hamburg 
> Germany 
>
> Commercial Reg. (Registergericht): Amtsgericht Hamburg, HRB 125175 
> Geschäftsführer: Lennart Koopmann (CEO) 
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/abf513aa-e4f8-42bc-b9d7-ec8fd381a8aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to