Difference between revisions of "Wikispooks:Site Status/Server upgrade issues"
m (add) |
|||
| (8 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
==Issues== | ==Issues== | ||
| − | === | + | ===Anonymous uploads form returns a 'connection refused' error=== |
| − | + | IPtables set to allow port 25 so not sure what's causing this yet - lowish priority. --[[User:Peter|Peter P]] ([[User talk:Peter|talk]]) 11:24, 16 January 2014 (GMT) | |
| − | === | + | ===IMAP mail server to set up=== |
| − | + | Site can still receive and send email but no Domain IMAP facility yet. --[[User:Peter|Peter P]] ([[User talk:Peter|talk]]) 08:14, 18 January 2014 (GMT) | |
| + | |||
| + | ===9 pages with invalid server index entries=== | ||
| + | SMW data refresh procedure revealed 9 entries with invalid ID indexes. The earlier imaging problems are likely caused by this rather than the Umlaut character. Still no response from techies about how to identify which page/entity the offending entries refer to since there is clearly not a 1:1 page:index number relationship. I've had a root around with phpMyAdmin but the potential for causing serious damage is too great for much of that. It does not seem to be causing any additional problems so I've put it on the back burner for now --[[User:Peter|Peter P]] ([[User talk:Peter|talk]]) 08:14, 18 January 2014 (GMT) | ||
Latest revision as of 08:18, 18 January 2014
This page is a to-do list of issues arising out of the Server upgrade of 16 January 2014
Please note anything odd here.
Contents
Issues
Anonymous uploads form returns a 'connection refused' error
IPtables set to allow port 25 so not sure what's causing this yet - lowish priority. --Peter P (talk) 11:24, 16 January 2014 (GMT)
IMAP mail server to set up
Site can still receive and send email but no Domain IMAP facility yet. --Peter P (talk) 08:14, 18 January 2014 (GMT)
9 pages with invalid server index entries
SMW data refresh procedure revealed 9 entries with invalid ID indexes. The earlier imaging problems are likely caused by this rather than the Umlaut character. Still no response from techies about how to identify which page/entity the offending entries refer to since there is clearly not a 1:1 page:index number relationship. I've had a root around with phpMyAdmin but the potential for causing serious damage is too great for much of that. It does not seem to be causing any additional problems so I've put it on the back burner for now --Peter P (talk) 08:14, 18 January 2014 (GMT)
