Skip to main content

User not in the sudoers file This incident will be reported

Image
By
User not in the sudoers file This incident will be reported can happens dues to multiple reasons and it’s up to us that how we identify the issue. We know that in UNIX like systems root is the super user account. It is a great mistake, if you have only and only root user in your operating system because a single mistake or wrong command can cause a great problem as well.

User not in the sudoers file This incident will be reported

Well, back to point, on Debian based Linux flavors this error can be a reason of broken sudo or easy term corrupted sudoers. Broken sudoers has multiple reason, most important are as below;
  1. User must resides in the sudo or admin group and one should not remove it.
  2. The /etc/sudoers file was altered to prevent users in sudo or admin group from elevating their privileges to that of root using sudo command.
  3. Confirm if the correct permission (dr--r----- or 0440) are setup on /etc/sudoers.
We need the sudo command to gain super user privileges to perform various task, if we face deny usage of sudo due to any reason, many of our crucial task might get delayed. I will discuss possible solutions in this post, if you have something more to share, please show up in comments and let me to add this in the post.

Solutions:

  • Sudo Privileges : You need to confirm that either you username has the sudoer privileges or you need to ask the system Administrator to add this user to sudoer. Here is the simple command, when can let you to check this;
    • sudo -l -U ftpadmin
     

  • Invoke Suoder Privileges : If you are assure that you are have the admin or sudoer priviledges than it might need us to to invoke sudoer privileges by simply adding su before any command. It will prompt for the root password and you can get your work done.
    • [root@localhost ~]# su [command]
Labels:

Comments

Post a Comment

Popular posts from this blog

Setting up per connection Limit Bandwidth on MikroTik Router

By
Generally, I do not prefer to add any unwanted restriction on the network user until its required due to some Administration reason. I know, there are more ways to tackle this setting up per connection Limit Bandwidth on MikroTik Router question comes into one’s mind but I resolve my concern while using MikroTik PCQs feature in MikroTik Queue Type and then calling this Queue Type to Simple Queue. There are more options for setting up per connection Limit Bandwidth on MikroTik Router but please share your concern to add anything else in this article. Let’s start to add our configurations; I am using WinBox for this Article but you can use anything you are convenient to use. Let’s start Step by Step procedure for Setting up per connection Limit Bandwidth on MikroTik Router, any version.  Setup Queue Types After Successful Login, click on Queues menu. Navigate to Queue Types and Press Add + (Plus Sign) to add a new Queue Type. Type a Name like in my scenario,...
Post a Comment
Read more

DsReplicaGetInfo failed with status 8453 0x2105 on Windows Server 2008

By
I have two Domain Controller in my envorinment, Primary Domain Controller is Windows Server 2003 based and Additional domain controller is Windows Server 2008 based. When I Installed New 2008 ADC and after some time, when I check with repadmin /showreps found the error.... DsReplicaGetInfo() failed with status 8453 (0x2105):Replication access was denied. I really worried about Solutions: [ DsReplicaGetInfo failed with status 8453 ]
1 comment
Read more

Event ID 1202 Source SceCli on domain controller - Solved

By
I was getting rapidly Event ID 1202 Source SceCli on my domain controller. Security policies were propagated with warning. 0x4b8: An extended error has occurred. Advanced help for this problem is available on http://support.microsoft.com. Query for "troubleshooting 1202 events". – Event ID 1202 Source SceCli It was a newly build Windows Server 2012 Domain Controller. I have scenario like this; Before: Primary Domain Controller: Windows Server 2003 (32-bit) Secondary Domain Controller: Windows Server 2008 (32-bit) Now: Primary Domain Controller: Windows Server 2012 Secondary Domain Controller: Windows Server 2008 (32-bit) After successfully DC promotion and after a week, I start getting Event ID 1202 on newly build server. L I tried various solutions but nothing was great except the below one; Solution ( Caution ):  Start > Type CMD > Run As Administrator (Open it on Windows Server 2012: Domain Controller)  Type   dcgpofix /ignoresche...
Post a Comment
Read more