The problem would appear that pam is reporting a system error, which fails your authentication. Are you supposed to be using pam?
Aki > On December 28, 2017 at 12:50 AM Howard Leadmon <how...@leadmon.net> wrote: > > > I hear what your saying, but if you read and follow the repo page, it > says run update, and then upgrade. Also as a test, I did remove the > old 2.2 code, and installed the new 2.3 code, and again authentication > fails. > > I am sure I may be missing something stupid, but the bottom line is, > how can I track down why it will not auth using PAM under the newer > code, when even looking at the auth modules, the configs appear to be > the same on 2.2 and 2.3, so I didn't see any adjustments I could > actually make.. > > > --- > Howard Leadmon > PBW Communications, LLC > http://www.pbwcomm.com > > On 12/27/2017 5:39 PM, Noel Butler wrote: > > Why on earth you think you could upgrade versions by using two unrelated > > and different repo's is beyond me. > > > > This has always been a problem, even back in the 90's with the RPMs, RH > > v say for example Fresh, because package maintainers will package > > differently. > > > > Its like trying to stick a cisco 1800 image on an ASR9K and expecting it > > to work perfectly. > > > > Though we don't use deb or rpm based systems and haven't for about 15 > > years, if I was to, I think I'd be using the creators version, and not a > > distro's version. > > >