Ошибка no such user

PostgreSQL 12.2
Red Hat Enterprise Linux Server release 7.9
PgBouncer 1.14

[databases]
* = host=127.0.0.1 port=5432 user=*

[pgbouncer]
logfile = /var/log/pgbouncer/pgbouncer.log
pidfile = /var/run/pgbouncer/pgbouncer.pid
listen_addr = ***.**.***.***
listen_port = 3306
auth_type = hba
auth_hba_file = /data/postgres/pg_hba.conf
admin_users = postgres
stats_users = postgres
pool_mode = session
ignore_startup_parameters = extra_float_digits
max_client_conn = 200
default_pool_size = 50
reserve_pool_size = 25
reserve_pool_timeout = 3
server_lifetime = 5
server_idle_timeout = 120
server_connect_timeout = 5
server_login_retry = 1
query_timeout = 60
query_wait_timeout = 60
client_idle_timeout = 60
client_login_timeout = 60
syslog=1
;;verbose=2

I am trying to set up and test PgBouncer with an already existing PostgreSQL 12 server but there must be something I am missing. I know my pg_hba file is properly set up, but when I try to connect using psql I get a «No such user» error.

psql -h HOST -U USER -p 3306 -d postgres
psql: error: could not connect to server: ERROR:  no such user: USER

From the log file

2021-04-27 09:53:36.112 EDT [6077] LOG kernel file descriptor limit: 1024 (hard: 4096); max_client_conn: 200, max expected fd use: 212
2021-04-27 09:53:36.113 EDT [6077] LOG listening on ********:3306
2021-04-27 09:53:36.113 EDT [6077] LOG listening on unix:/tmp/.s.PGSQL.3306
2021-04-27 09:53:36.114 EDT [6077] LOG process up: PgBouncer 1.14.0, libevent 2.0.21-stable (epoll), adns: evdns2, tls: OpenSSL 1.0.2k-fips  26 Jan 2017
2021-04-27 09:53:38.806 EDT [6077] LOG C-0x559d9430a420: (nodb)/(nouser)@********:34744 registered new auto-database: db=postgres
2021-04-27 09:53:38.806 EDT [6077] LOG C-0x559d9430a420: (nodb)/(nouser)@********:34744 closing because: no such user: ********(age=0s)
2021-04-27 09:53:38.806 EDT [6077] WARNING C-0x559d9430a420: (nodb)/(nouser)@********:34744 pooler error: no such user: ********
2021-04-27 09:53:38.806 EDT [6077] LOG C-0x559d9430a420: (nodb)/(nouser)@********:34744 login failed: db=postgres user=********
2021-04-27 09:54:36.113 EDT [6077] LOG stats: 0 xacts/s, 0 queries/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us
2021-04-27 09:55:36.113 EDT [6077] LOG stats: 0 xacts/s, 0 queries/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us
2021-04-27 09:56:36.113 EDT [6077] LOG stats: 0 xacts/s, 0 queries/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us
2021-04-27 09:57:36.113 EDT [6077] LOG stats: 0 xacts/s, 0 queries/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us
2021-04-27 09:58:36.113 EDT [6077] LOG stats: 0 xacts/s, 0 queries/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us
2021-04-27 09:59:36.113 EDT [6077] LOG stats: 0 xacts/s, 0 queries/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us
2021-04-27 10:00:36.113 EDT [6077] LOG stats: 0 xacts/s, 0 queries/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us
2021-04-27 10:01:36.113 EDT [6077] LOG stats: 0 xacts/s, 0 queries/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us
2021-04-27 10:02:18.620 EDT [6077] LOG C-0x559d9430a420: (nodb)/(nouser)@********:34832 closing because: no such user: ********(age=0s)
2021-04-27 10:02:18.621 EDT [6077] WARNING C-0x559d9430a420: (nodb)/(nouser)@********:34832 pooler error: no such user: ********
2021-04-27 10:02:18.621 EDT [6077] LOG C-0x559d9430a420: (nodb)/(nouser)@********:34832 login failed: db=postgres user=********
2021-04-27 10:02:36.113 EDT [6077] LOG stats: 0 xacts/s, 0 queries/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us
2021-04-27 10:03:36.113 EDT [6077] LOG stats: 0 xacts/s, 0 queries/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us

I can provide more details if needed.

Источник

One common error you can get when sending email is the “550 No Such User here” error. This error occurs when the sending email is rejected because the username cannot be found or is not accessible by the server. There are several reasons why you would get a “550 No Such User Here” error.

  • Mail file permissions are not readable or are incorrect.
  • The email address was typed incorrectly.
  • MX records are incorrect ( pointing to the wrong server ).
  • Email does not route correctly ( Remote / Local domains ).

This error can go both ways, meaning, people sending to your server may get the error and when you send from your server to another you may get the error. Depending on where the error bounce is generated from will determine what you can do about fixing the error.

If you get “550 No Such User Here” bounces sending from your server to another server, you most likely will need to contact the host or email administrator of the server you are emailing to fix it.

If you are getting complaints that people sending to your server are getting this bounce, you can check / change the settings on your servers end. Below are the reasons why the 550 error may occur when you email.

Mail file permissions are not readable or are incorrect

All our servers store email in the “mail” directory of the “home” folder of your cPanel account. If the file permissions are corrupted ( sometimes caused by server moves, back up restorations, or recently uploaded files through FTP, etc.) you will get this error for all your emails. This is a simple fix. You can contact tech support to have the file permissions fixed on your server. On VPS and Dedicated servers, you can run the following from command line:

[[email protected]#### ~]$ fixperms userna5

This will reset all your file and folder permissions to folders 755 and files 644 for teh cPanle user userna5. If the email bounce is coming to you when you send to another server and it’s permissions related, the person you are emailing will need to contact their hosting provider to fix the permissions on their end.

The email address was typed incorrectly

“550 No Such User Here” Errors can occur when the email address you are sending to is typed incorrectly. In this case, just make sure you have the email address spelled correctly.

MX records are incorrect ( pointing to the wrong server )

If you recently moved your domain to InMotion Hosting and you started receiving these errors, you may have a DNS nameserver or MX record problem. The MX records point your email address to a specific server. If the MX record is pointing your domain to the old hosting company and you removed all your email accounts off that server, when you go to send your email, you will get the “550 No Such User Here” error. You will want to check the following through command line:

[[email protected]#### ~]$$ dig example.com mx ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.6 <<>> example.com mx ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8149 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3 ;; QUESTION SECTION: ;example.com.                 IN      MX ;; ANSWER SECTION: example.com.          14400   IN      MX      0 example.com. ;; AUTHORITY SECTION: example.com.          54747   IN      NS      ns2.inmotionhosting.com. example.com.          54747   IN      NS      ns1.inmotionhosting.com. ;; ADDITIONAL SECTION: example.com.          13322   IN      A       66.117.4.177 ns1.inmotionhosting.com. 11994   IN      A       74.124.210.242 ns2.inmotionhosting.com. 11994  IN      A       70.39.150.2

The example above shows that domain example.com points to the ns1.inmotionhosting.com and ns2.inmotionhosting.com nameservers and that the MX routes to the InMotion Hosting server.

Make sure your nameservers are pointing to us. If your nameservers do not point to our server, then your domain will not route to our server unless you make special DNS changes at the host the nameservers point to.

Make sure the MX records for your domain are sending to the correct server. If your domain does point to the correct server, check the MX records to see if the email is pointing to the correct server in the cPanel MX entry.

If your nameservers and DNS are correct, then you will need to check the email routing. If the bounce message is from you sending to another server, then the person receiving the email will need to check with their email provider for a resolution.

Email does not route correctly ( Remote / Local domains )

In the case that you are receiving bounces to a specific email address, you will need to find the MX records and the nameservers for the receiving domains DNS. Run the following DIG in the Linux command line to find the Receiving servers nameservers.

To find out if your domain is on the receiving email servers DNS nameserver, you can DIG the domain for their nameservers. Once you get the nameservers for the receiving domain, you can check the DNS for your domain using their nameservers. Below will explain in detail.

Dig the receiving server domain to find the nameservers:

Below shows what a DNS MX record DIG looks like for notexample.com.

[[email protected]#### ~]$ dig notexample.com mx ; <<>> DIG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.6 <<>> notexample.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8587 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;notexample.com.                 IN      A ;; ANSWER SECTION: notexample.com.          14400   IN      MX      0 notexample.com. ;; AUTHORITY SECTION: notexample.com.          85619   IN      NS      ns1.somenameserver.com. notexample.com.          85619   IN      NS      ns2.somenameserver.com. ;; ADDITIONAL SECTION: notexample.com.          13322   IN      A       25.22.80.62 ns2.somenameserver.com. 18391 IN     A       25.22.80.62 ns1.somenameserver.com. 18391 IN     A       25.22.67.43 ;; Query time: 1 msec ;; SERVER: 74.124.198.200#53(74.124.198.200) ;; WHEN: Thu Mar  7 06:08:06 2013 ;; MSG SIZE  rcvd: 136

The results of this DIG shows that the nameservers for the receiving server notexample.com has the nameservers of ns1.somenameserver.com and ns2.somenameserver.com. The MX record points to notexample.com which has an IP that points to the server the nameservers are on. Next you can check your domain in the receiving server nameservers.

Checking if your domain is in another servers DNS:

Now that you have the receiving server nameservers for the notexample.com domain, you can DIG the DNS records at the receiving servers end to see if your domain is in their DNS nameserver. The following is an example of the DIG command in shell that will look up example.com on the notexample.com server.

dig @ns1.somenameserver.org example.com ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.6 <<>> @ns1.somenameserver.org example.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11023 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;example.com.            IN      A ;; ANSWER SECTION: example.com.     14400   IN      A       70.39.251.58 ;; AUTHORITY SECTION: example.com.     86400   IN      NS      ns2.somenameserver.org. example.com.     86400   IN      NS      ns1.somenameserver.org. ;; ADDITIONAL SECTION: ns1.somenameserver.org. 14400 IN      A       70.39.251.58 ns2.somenameserver.org. 14400 IN      A       70.39.251.58 ;; Query time: 66 msec ;; SERVER: 70.39.251.58#53(70.39.251.58) ;; WHEN: Fri Mar  8 06:16:18 2013 ;; MSG SIZE  rcvd: 140

The previous response shows that example.com is in the DNS on the notexample.com server. This means that the emails sent to notexample.com are seeing example.com in their DNS, looking for the email address on the notexample.com server, and rejecting it because there is no email address on the server.

To fix this, you will need to contact the hosting company or the domain owner that you are sending to, telling them that your emails cannot go through to their server because your domain is in their DNS. They will ned to “Kill the DNS“, change the routing to remote on the receiving server, or remove your domain from their DNS nameserver.

If your domain is not in their DNS nameserver:

If example.com was NOT found in the nameserver on the receiving server you will get the following not found response.

dig @ns1.inmotionhosting.com google.com ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.6 <<>> @ns1.inmotionhosting.com google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 63529 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;google.com.                    IN      A ;; Query time: 0 msec ;; SERVER: 74.124.210.242#53(74.124.210.242) ;; WHEN: Fri Mar  8 06:20:03 2013 ;; MSG SIZE  rcvd: 28

In this case, you can try checking your email routing. If you are sending from your server with us, you will need to set the email routing to local in your MX entry of your cPanel. If you are using a 3rd party application like Google APPs, you will need the routing set to remote.

If this does not fix the problem, then you will want to contact tech support to find out if there is a routing issue with your DNS.

Источник

Symptoms

When a domain controller that is running Windows Server 2008 is in the shutdown or restart process, the domain controller may respond to authentication requests incorrectly. The incorrect response by the domain controller might be to return the «NO_SUCH_USER (0xc0000064)» status code or the «KDC_ERR_C_PRINCIPAL_UNKNOWN» error to any one of the following computers:

  • The domain member computer that originated the authentication request

  • An application server

  • The domain controller that forward the authentication request to the authenticating domain controller by using pass-through authentication

Cause

This issue occurs because the Net Logon service (Netlogon.dll) manages the returned status incorrectly.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 Service Pack 2 (SP2) and have the Active Directory Domain Service (AD DS) role installed.

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2008 file information notes

  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    Version

    Product

    SR_Level

    Service branch

    6.0.600
    2.
    22xxx

    Windows Server 2008

    SP2

    LDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows Server 2008» section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Kdcsvc.dll

6.0.6002.22405

313,344

14-May-2010

18:14

x86

Kdcsvc.mof

Not applicable

5,300

03-Apr-2009

21:47

Not applicable

Ksecdd.sys

6.0.6002.22152

439,880

30-Jul-2009

17:42

x86

Lsasrv.dll

6.0.6002.22405

1,260,032

14-May-2010

18:14

x86

Lsasrv.mof

Not applicable

13,780

03-Apr-2009

21:33

Not applicable

Lsass.exe

6.0.6002.22405

9,728

14-May-2010

15:52

x86

Secur32.dll

6.0.6002.22405

72,704

14-May-2010

18:17

x86

Wdigest.dll

6.0.6002.22405

175,104

14-May-2010

18:18

x86

Netlogon.dll

6.0.6002.22405

592,896

14-May-2010

18:16

x86

Nlsvc.mof

Not applicable

2,873

03-Apr-2009

21:24

Not applicable

Msv1_0.dll

6.0.6002.22405

218,624

14-May-2010

18:15

x86
For all supported x64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Kdcsvc.dll

6.0.6002.22405

407,040

14-May-2010

18:21

x64

Kdcsvc.mof

Not applicable

5,300

03-Apr-2009

21:07

Not applicable

Ksecdd.sys

6.0.6002.22152

515,656

30-Jul-2009

17:42

x64

Lsasrv.dll

6.0.6002.22405

1,690,112

14-May-2010

18:21

x64

Lsasrv.mof

Not applicable

13,780

03-Apr-2009

21:02

Not applicable

Lsass.exe

6.0.6002.22405

11,264

14-May-2010

16:10

x64

Secur32.dll

6.0.6002.22405

94,720

14-May-2010

18:24

x64

Wdigest.dll

6.0.6002.22405

205,312

14-May-2010

18:25

x64

Netlogon.dll

6.0.6002.22405

717,312

14-May-2010

18:22

x64

Nlsvc.mof

Not applicable

2,873

03-Apr-2009

20:58

Not applicable

Msv1_0.dll

6.0.6002.22405

269,312

14-May-2010

18:22

x64

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

File name

Update.mum

File version

Not applicable

File size

3,845

Date (UTC)

18-May-2010

Time (UTC)

05:11

Platform

Not applicable

File name

X86_009e1cf91cef6ce4fe4889fcc7afece2_31bf3856ad364e35_6.0.6002.22405_none_3ca83560369e735d.manifest

File version

Not applicable

File size

703

Date (UTC)

18-May-2010

Time (UTC)

05:11

Platform

Not applicable

File name

X86_1cedcb653984066f13847ab2b0d04129_31bf3856ad364e35_6.0.6002.22405_none_fedca755150af31d.manifest

File version

Not applicable

File size

720

Date (UTC)

18-May-2010

Time (UTC)

05:11

Platform

Not applicable

File name

X86_3352e89ec35b3c9da6cf561f3109246a_31bf3856ad364e35_6.0.6002.22405_none_3601eba5f27a7a52.manifest

File version

Not applicable

File size

705

Date (UTC)

18-May-2010

Time (UTC)

05:11

Platform

Not applicable

File name

X86_9f2efa1b4fee1225b22e5dacc5f83a38_31bf3856ad364e35_6.0.6002.22405_none_68bad95d04fc4399.manifest

File version

Not applicable

File size

1,036

Date (UTC)

18-May-2010

Time (UTC)

05:11

Platform

Not applicable

File name

X86_microsoft-windows-k..distribution-center_31bf3856ad364e35_6.0.6002.22405_none_8e2ce3d9aa804577.manifest

File version

Not applicable

File size

42,276

Date (UTC)

14-May-2010

Time (UTC)

19:56

Platform

Not applicable

File name

X86_microsoft-windows-lsa_31bf3856ad364e35_6.0.6002.22405_none_a8bfa64b730a9ac1.manifest

File version

Not applicable

File size

34,354

Date (UTC)

14-May-2010

Time (UTC)

19:55

Platform

Not applicable

File name

X86_microsoft-windows-security-digest_31bf3856ad364e35_6.0.6002.22405_none_3d4266a092f47654.manifest

File version

Not applicable

File size

9,924

Date (UTC)

14-May-2010

Time (UTC)

19:59

Platform

Not applicable

File name

X86_microsoft-windows-security-netlogon_31bf3856ad364e35_6.0.6002.22405_none_002cd2cc4e394ae2.manifest

File version

Not applicable

File size

22,701

Date (UTC)

14-May-2010

Time (UTC)

19:57

Platform

Not applicable

File name

X86_microsoft-windows-security-ntlm_31bf3856ad364e35_6.0.6002.22405_none_7f28085c78ca25a3.manifest

File version

Not applicable

File size

18,890

Date (UTC)

14-May-2010

Time (UTC)

19:57

Platform

Not applicable
Additional files for all supported x64-based versions of Windows Server 2008

File name

Amd64_2ad761ee8fa232916ecbb424f975d388_31bf3856ad364e35_6.0.6002.22405_none_1cb663eafce86ce1.manifest

File version

Not applicable

File size

724

Date (UTC)

18-May-2010

Time (UTC)

05:11

Platform

Not applicable

File name

Amd64_5ff669bbd17b21c952b3cd1a15c74e84_31bf3856ad364e35_6.0.6002.22405_none_7a17d3e6b5ee5463.manifest

File version

Not applicable

File size

1,726

Date (UTC)

18-May-2010

Time (UTC)

05:11

Platform

Not applicable

File name

Amd64_836347a71f120f5803e8657bbd205740_31bf3856ad364e35_6.0.6002.22405_none_cde15f892b23164a.manifest

File version

Not applicable

File size

1,060

Date (UTC)

18-May-2010

Time (UTC)

05:11

Platform

Not applicable

File name

Amd64_a7d63251f74c5232ccf1861766ceaab1_31bf3856ad364e35_6.0.6002.22405_none_80a0e6d86e5c1b49.manifest

File version

Not applicable

File size

1,056

Date (UTC)

18-May-2010

Time (UTC)

05:11

Platform

Not applicable

File name

Amd64_microsoft-windows-k..distribution-center_31bf3856ad364e35_6.0.6002.22405_none_ea4b7f5d62ddb6ad.manifest

File version

Not applicable

File size

42,320

Date (UTC)

14-May-2010

Time (UTC)

20:01

Platform

Not applicable

File name

Amd64_microsoft-windows-lsa_31bf3856ad364e35_6.0.6002.22405_none_04de41cf2b680bf7.manifest

File version

Not applicable

File size

34,442

Date (UTC)

14-May-2010

Time (UTC)

20:00

Platform

Not applicable

File name

Amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.0.6002.22405_none_996102244b51e78a.manifest

File version

Not applicable

File size

9,948

Date (UTC)

14-May-2010

Time (UTC)

20:04

Platform

Not applicable

File name

Amd64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.0.6002.22405_none_5c4b6e500696bc18.manifest

File version

Not applicable

File size

23,180

Date (UTC)

14-May-2010

Time (UTC)

20:02

Platform

Not applicable

File name

Amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.0.6002.22405_none_db46a3e0312796d9.manifest

File version

Not applicable

File size

18,926

Date (UTC)

14-May-2010

Time (UTC)

20:02

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

3,877

Date (UTC)

18-May-2010

Time (UTC)

05:11

Platform

Not applicable

File name

Wow64_microsoft-windows-lsa_31bf3856ad364e35_6.0.6002.22405_none_0f32ec215fc8cdf2.manifest

File version

Not applicable

File size

21,959

Date (UTC)

14-May-2010

Time (UTC)

19:51

Platform

Not applicable

File name

Wow64_microsoft-windows-security-digest_31bf3856ad364e35_6.0.6002.22405_none_a3b5ac767fb2a985.manifest

File version

Not applicable

File size

10,140

Date (UTC)

14-May-2010

Time (UTC)

19:51

Platform

Not applicable

File name

Wow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.0.6002.22405_none_66a018a23af77e13.manifest

File version

Not applicable

File size

18,332

Date (UTC)

14-May-2010

Time (UTC)

19:51

Platform

Not applicable

File name

Wow64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.0.6002.22405_none_e59b4e32658858d4.manifest

File version

Not applicable

File size

17,843

Date (UTC)

14-May-2010

Time (UTC)

19:51

Platform

Not applicable
Источник

This error message is returned by wrapper.c:

struct passwd *xgetpwuid_self(void)
{
        struct passwd *pw;

        errno = 0;
        pw = getpwuid(getuid());
        if (!pw)
                die(_("unable to look up current user in the passwd file: %s"),
                 errno ? strerror(errno) : _("no such user"));
        return pw;
}

That means the common library getpwuid function doesn’t find a password entry in /etc/passwd for the user account under which the git process is called

It is like the nscd service didn’t know how to resolve some services.

Ask your admin to double-check the account jail directory (let’s call it $D), as illustrated in this article. Especially its $D/etc folder:

cp -fv /etc/{group,prelink.cache,services,adjtime,shells,gshadow,shadow,hosts.deny,localtime,nsswitch.conf,nscd.conf,prelink.conf,protocols,hosts,passwd,ld.so.cache,ld.so.conf,resolv.conf,host.conf} $D/et

Источник

cqc0988

Posts: 1
Joined: 2015/11/30 21:30:09

SSSD with AD — No such user

Dear all,

I am new with SSSD and like to use it to authenticate Windows AD users on our Linux (CentOS 7) machine. After joining the Linux to the Windows Active Directory by using «realm join mydomain -U domainadminuser» successfully, I am able to see the computer account built in AD.

Difficulties:
Experiencing some difficulties with the user identification. After joining the domain successfully, on Linux machine, I was trying to use the command “id” to identify the domain users but failed. And of course, it won’t let me to “ssh” into the system against the AD accounts. Please help

BTW, from Linux, it can ping / find DC and I have tried to disable the firewalld on the linux to ensure there is no blocking issue from the linux end, but no luck.

# id domainuser@mydomain
id: domainuser@mydomain: no such user

Here this the output from «realm list»

[tigeruser@linux etc]# sudo realm list
mydomain
type: kerberos
realm-name: MYDOMAIN
domain-name: mydomain
configured: kerberos-member
server-software: active-directory
client-software: sssd
required-package: oddjob
required-package: oddjob-mkhomedir
required-package: sssd
required-package: adcli
required-package: samba-common
login-formats: %U@mydomain
login-policy: allow-realm-logins

t3kg33k

Posts: 24
Joined: 2016/02/26 19:45:27

Re: SSSD with AD — No such user

Post

by t3kg33k » 2016/05/19 12:39:29

I’m having the same issue.
Anyone know how to fix this?

ephos

Posts: 1
Joined: 2016/05/23 14:43:25

Re: SSSD with AD — No such user

Post

by ephos » 2016/05/23 14:47:26

I am also having this issue.

saerom

Posts: 1
Joined: 2016/05/27 11:14:32

Re: SSSD with AD — No such user

Post

by saerom » 2016/05/27 11:24:38

Also having this problem. When setting ldap_id_mapping = True, no problem to lookup users with «id» or «getent». But we need to use the POSIX attributes in AD…

hema.arun

Posts: 21
Joined: 2017/02/06 11:56:26

Re: SSSD with AD — No such user

Post

by hema.arun » 2019/12/31 11:46:01

Remove all custom values in /etc/krb5.conf.
Restart sssd service and this resolved my same issue.
Now I am getting AD user list.

idiot

Posts: 4
Joined: 2022/01/29 12:42:30

Re: SSSD with AD — No such user

Post

by idiot » 2022/01/29 16:58:32

@hema.arun, I am also facing the same issue.

It will be great if you could share the details of the files.

Maryam_Trend

Posts: 1
Joined: 2022/04/11 23:01:57

Re: SSSD with AD — No such user

Post

by Maryam_Trend » 2022/04/11 23:04:33

1. First you create two users called adusera and aduserb in Windows 2019 AD

2. Login as root and edit SSSD (System Security Services Daemon) configuration as follows so that you could login to an AD user accounts without domain name. (eg: login as adusera instead of adusera@adatum.com).
Use the gedit text editor in GNOME desktop
[root@fedora ~]# gedit /etc/sssd/sssd.conf
Go to the line 16
Change the line to
use_fully_qualified_names = False

3. Restart the SSSD
[root@fedora ~]# systemctl restart sssd

derokk

Posts: 5
Joined: 2022/08/16 17:44:27

Re: SSSD with AD — No such user

Post

by derokk » 2022/08/17 18:24:33

Hello I will share you here my config files for SSSD and it works very well:

/etc/sssd/sssd.conf
[sssd]
domains = MY_AD.DOMAIN.COM
config_file_version = 2
services = nss, pam

[domain/intranet.hybride.com]
ad_domain = MY_AD.DOMAIN.COM
krb5_realm = MY_AD.DOMAIN.COM
realmd_tags = manages-system joined-with-samba
cache_credentials = True
id_provider = ad
krb5_store_password_if_offline = True
default_shell = /bin/bash
ldap_id_mapping = True
use_fully_qualified_names = False
fallback_homedir = /home/%u
access_provider = ad
ldap_idmap_autorid_compat = True

/etc/krb5.conf
# Configuration snippets may be placed in this directory as well
includedir /etc/krb5.conf.d/

includedir /var/lib/sss/pubconf/krb5.include.d/
[logging]
default = FILE:/var/log/krb5libs.log
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmind.log

[libdefaults]
dns_lookup_realm = false
ticket_lifetime = 24h
renew_lifetime = 7d
forwardable = true
rdns = false
pkinit_anchors = FILE:/etc/pki/tls/certs/ca-bundle.crt
# default_realm = EXAMPLE.COM
default_ccache_name = KEYRING:persistent:%{uid}

default_realm = MY_AD.DOMAIN.COM
[realms]
MY_AD.DOMAIN.COM = {
kdc = DomainController.my_ad.domain.com
kpasswd_server = DomainController.my_ad.domain.com
admin_server = DomainController.my_ad.domain.com
default_domain = MY_AD.DOMAIN.COM
}

[domain_realm]
# .example.com = EXAMPLE.COM
# example.com = EXAMPLE.COM
my_ad.domain.com = MY_AD.DOMAIN.COM
.my_ad.domain.com = MY_AD.DOMAIN.COM

Remember your sssd.conf file must be 600

Restart your service sssd and take a cookie :)

Cheers!

Источник

Понравилась статья? Поделить с друзьями:
  • Ошибка no such process transmission
  • Ошибка nisa wp симс 4 как исправить
  • Ошибка nintendo 3ds an exception occurred
  • Ошибка nightingale destiny 2 на пк
  • Ошибка nicks coop postal 2