cgspace-notes/content/post/2017-10.md

---
title: "October, 2017"
date: 2017-10-01T08:07:54+03:00
author: "Alan Orth"
tags: ["Notes"]
---

## 2017-10-01

- Peter emailed to point out that many items in the [ILRI archive collection](https://cgspace.cgiar.org/handle/10568/2703) have multiple handles:

```
http://hdl.handle.net/10568/78495||http://hdl.handle.net/10568/79336
```

- There appears to be a pattern but I'll have to look a bit closer and try to clean them up automatically, either in SQL or in OpenRefine
- Add Katherine Lutz to the groups for content sumission and edit steps of the CGIAR System collections

<!--more-->

## 2017-10-02

- Peter Ballantyne said he was having problems logging into CGSpace with "both" of his accounts (CGIAR LDAP and personal, apparently)
- I looked in the logs and saw some LDAP lookup failures due to timeout but also strangely a "no DN found" error:

```
2017-10-01 20:24:57,928 WARN  org.dspace.authenticate.LDAPAuthentication @ anonymous:session_id=CA0AA5FEAEA8805645489404CDCE9594:ip_addr=41.204.190.40:ldap_attribute_lookup:type=failed_search javax.naming.CommunicationException\colon; svcgroot2.cgiarad.org\colon;3269 [Root exception is java.net.ConnectException\colon; Connection timed out (Connection timed out)]
2017-10-01 20:22:37,982 INFO  org.dspace.authenticate.LDAPAuthentication @ anonymous:session_id=CA0AA5FEAEA8805645489404CDCE9594:ip_addr=41.204.190.40:failed_login:no DN found for user pballantyne
```

- I thought maybe his account had expired (seeing as it's was the first of the month) but he says he was finally able to log in today
- The logs for yesterday show fourteen errors related to LDAP auth failures:

```
$ grep -c "ldap_authentication:type=failed_auth" dspace.log.2017-10-01
14
```

- For what it's worth, there are no errors on any other recent days, so it must have been some network issue on Linode or CGNET's LDAP server
Add notes for 2017-10-01 2017-10-01 07:13:31 +02:00			`---`
			`title: "October, 2017"`
			`date: 2017-10-01T08:07:54+03:00`
			`author: "Alan Orth"`
			`tags: ["Notes"]`
			`---`

			`## 2017-10-01`

			`- Peter emailed to point out that many items in the [ILRI archive collection](https://cgspace.cgiar.org/handle/10568/2703) have multiple handles:`

			```
			`http://hdl.handle.net/10568/78495\|\|http://hdl.handle.net/10568/79336`
			```

			`- There appears to be a pattern but I'll have to look a bit closer and try to clean them up automatically, either in SQL or in OpenRefine`
Update notes 2017-10-01 12:44:37 +02:00			`- Add Katherine Lutz to the groups for content sumission and edit steps of the CGIAR System collections`
Add notes for 2017-10-01 2017-10-01 07:13:31 +02:00
			`<!--more-->`
Update notes 2017-10-01 12:44:37 +02:00
Add notes for 2017-10-02 2017-10-02 07:14:44 +02:00			`## 2017-10-02`

			`- Peter Ballantyne said he was having problems logging into CGSpace with "both" of his accounts (CGIAR LDAP and personal, apparently)`
			`- I looked in the logs and saw some LDAP lookup failures due to timeout but also strangely a "no DN found" error:`

			```
			`2017-10-01 20:24:57,928 WARN org.dspace.authenticate.LDAPAuthentication @ anonymous:session_id=CA0AA5FEAEA8805645489404CDCE9594:ip_addr=41.204.190.40:ldap_attribute_lookup:type=failed_search javax.naming.CommunicationException\colon; svcgroot2.cgiarad.org\colon;3269 [Root exception is java.net.ConnectException\colon; Connection timed out (Connection timed out)]`
			`2017-10-01 20:22:37,982 INFO org.dspace.authenticate.LDAPAuthentication @ anonymous:session_id=CA0AA5FEAEA8805645489404CDCE9594:ip_addr=41.204.190.40:failed_login:no DN found for user pballantyne`
			```

Update notes for 2017-10-02 2017-10-02 07:31:19 +02:00			`- I thought maybe his account had expired (seeing as it's was the first of the month) but he says he was finally able to log in today`
			`- The logs for yesterday show fourteen errors related to LDAP auth failures:`

			```
			`$ grep -c "ldap_authentication:type=failed_auth" dspace.log.2017-10-01`
			`14`
			```

			`- For what it's worth, there are no errors on any other recent days, so it must have been some network issue on Linode or CGNET's LDAP server`