Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

uac: bad error in log #643

Closed
snen opened this issue May 27, 2016 · 7 comments
Closed

uac: bad error in log #643

snen opened this issue May 27, 2016 · 7 comments

Comments

@snen
Copy link
Contributor

snen commented May 27, 2016

there is define in uac_reg.c (define reg_db_set_attr(attr, pos)) which may generate logs like this:

empty value not allowed for column[2]='l_domain' - ignoring record

really, record was added, so it should be converted to WARNING or it is neсessary add any more restrict logic

@miconda
Copy link
Member

miconda commented May 27, 2016

I guess you used it to refresh one record, because the process of loading the records at startup should ignore such records. reg_db_set_attr() triggers 'continue' in such case and it is used in a for-loop.

I am going to push a patch that will ignore also for the refresh operation. In that case reg_db_set_attr() was used alone, not within a loop.

miconda added a commit that referenced this issue May 27, 2016
- reg_db_set_attr() does a continue on empty value, but for this
  operation was not used inside a loop
- reported by Dmitri Savolainen, GH #643
@snen
Copy link
Contributor Author

snen commented May 27, 2016

it is startup error also

@miconda
Copy link
Member

miconda commented May 27, 2016

It is error indeed, but the record should not be added in that case, right?

@snen
Copy link
Contributor Author

snen commented May 27, 2016

record is added
kamcmd> uac.reg_dump
{
l_uuid: 000112838
l_username: 000112838
l_domain:
r_username: 000112838
.......
flags: 20
...........

}

@miconda
Copy link
Member

miconda commented May 27, 2016

Obviously -- reg_db_set_attr() is a while loop itself so the continue applied there.

Pushed another patch -- can you test it? If all ok, I will backport.

@snen
Copy link
Contributor Author

snen commented May 27, 2016

it works as expected, thanks!

@snen snen closed this as completed May 27, 2016
@miconda
Copy link
Member

miconda commented May 27, 2016

Thanks for reporting and testing, I will backport.

While it could have been ok without domain, the other attributes are important and same check was done for all.

miconda added a commit that referenced this issue May 27, 2016
- reg_db_set_attr() does a continue on empty value, but for this
  operation was not used inside a loop
- reported by Dmitri Savolainen, GH #643

(cherry picked from commit a34b382)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants