Solr unable to index certain nodes


#1

I’m getting solr errors when certain nodes are indexed:

Oct 25, 2011 11:19:13 PM org.apache.solr.common.SolrException log
SEVERE: org.apache.solr.common.SolrException: ParseError at [row,col]:[2,44199]
Message: Element type “field” must be followed by either attribute
specifications, “>” or “/>”.

I ran chef-indexer in debug mode and got the xml it was sending to
solr, ran that through an XML validator and it shows invalid XML from
the DMI BIOS info:

“Characteristics”: {
“CGA/mono video services are supported (int 10h)”: null,
“5.25”/360 KB floppy services are supported (int 13h)": null,
“5.25”/1.2 MB floppy services are supported (int 13h)": null,

I think the slashes are tripping it up. All the nodes that are failing
to index are running Ohai 0.6.x whereas the nodes running 0.5 index
just fine. Ohai 0.6.0 started including a lot more DMI information.
This is with Chef 0.9.18 on both client and server.

I created OHAI-309 for this.


#2

On Tue, Oct 25, 2011 at 5:58 PM, Eric Heydrick eheydrick@gmail.com wrote:

I’m getting solr errors when certain nodes are indexed:

Oct 25, 2011 11:19:13 PM org.apache.solr.common.SolrException log
SEVERE: org.apache.solr.common.SolrException: ParseError at [row,col]:[2,44199]
Message: Element type “field” must be followed by either attribute
specifications, “>” or “/>”.

I ran chef-indexer in debug mode and got the xml it was sending to
solr, ran that through an XML validator and it shows invalid XML from
the DMI BIOS info:

“Characteristics”: {
“CGA/mono video services are supported (int 10h)”: null,
“5.25”/360 KB floppy services are supported (int 13h)": null,
“5.25”/1.2 MB floppy services are supported (int 13h)": null,

I think the slashes are tripping it up. All the nodes that are failing
to index are running Ohai 0.6.x whereas the nodes running 0.5 index
just fine. Ohai 0.6.0 started including a lot more DMI information.
This is with Chef 0.9.18 on both client and server.

I created OHAI-309 for this.

Upgrading the server from 0.9.18 to 0.10.4 fixed this for me.


#3

Check if gem fast_xs is installed, if not run gem install fast_xs.

Brian Smith
Senior Network Engineer . Bonnier Corporation
brian.smith@bonniercorp.com

On Tue, Oct 25, 2011 at 8:58 PM, Eric Heydrick eheydrick@gmail.com wrote:

I’m getting solr errors when certain nodes are indexed:

Oct 25, 2011 11:19:13 PM org.apache.solr.common.SolrException log
SEVERE: org.apache.solr.common.SolrException: ParseError at
[row,col]:[2,44199]
Message: Element type “field” must be followed by either attribute
specifications, “>” or “/>”.

I ran chef-indexer in debug mode and got the xml it was sending to
solr, ran that through an XML validator and it shows invalid XML from
the DMI BIOS info:

“Characteristics”: {
“CGA/mono video services are supported (int 10h)”: null,
“5.25”/360 KB floppy services are supported (int 13h)": null,
“5.25”/1.2 MB floppy services are supported (int 13h)": null,

I think the slashes are tripping it up. All the nodes that are failing
to index are running Ohai 0.6.x whereas the nodes running 0.5 index
just fine. Ohai 0.6.0 started including a lot more DMI information.
This is with Chef 0.9.18 on both client and server.

I created OHAI-309 for this.