Using 32-bit 2.x version on CentOS 6, a successful metadata output looks like:
sogod [1617]: |SOGo| do traverse name: 'SOGo'
sogod [1617]: |SOGo| do traverse name: 'saml2-metadata'
sogod [1617]: |SOGo| set clientObject: <SOGo[0x0xb8a2839c]: name=SOGo>
sogod [1617]: |SOGo| request took 0.067427 seconds to execute
sogod [1617]: <0x0xb8b8be7c[WOResponse]> Zipping of response disabled
sogod [1617]: x.x.x.x "GET /SOGo/saml2-metadata HTTP/1.1" 200 3935/0 0.094 - - 2M

while using 64-bit 3.x version on CentOS 7, the unsuccessful metadata output is:
sogod [23400]: |SOGo| traverse(acquire): SOGo => saml2-metadata
sogod [23400]: |SOGo| do traverse name: 'SOGo'
sogod [23400]: |SOGo| do traverse name: 'saml2-metadata'
sogod [23400]: [ERROR] [so-action 0x0x7ff21dc4f030 SOGoSAML2Actions] did not find action class: SOGoSAML2Actions
sogod [23400]: [ERROR] [so-action 0x0x7ff21d9c9a90 SOGoSAML2Actions] did not find method 'SOGoSAML2Actions'
sogod [23400]: [ERROR] [so-action 0x0x7ff21df07d80 SOGoSAML2Actions] did not find action class: SOGoSAML2Actions
sogod [23400]: [ERROR] [so-action 0x0x7ff21d9c9a90 SOGoSAML2Actions] did not find method 'SOGoSAML2Actions'
sogod [23400]: [ERROR] [so-action 0x0x7ff21df17860 SOGoSAML2Actions] did not find action class: SOGoSAML2Actions
sogod [23400]: [ERROR] [so-action 0x0x7ff21d9c9a90 SOGoSAML2Actions] did not find method 'SOGoSAML2Actions'
sogod [23400]: |SOGo| traverse miss: name=saml2-metadata, acquire: i=1,count=2
sogod [23400]: |SOGo| miss is last object.
sogod [23400]: |SOGo| got no error for miss.
sogod [23400]: |SOGo| Note: next object is nil, but currentObject is not callable: <SOGo[0x0x7ff21d941c40]: name=SOGo>
sogod [23400]: |SOGo| request took 0.078251 seconds to execute
sogod [23400]: x.x.x.x env=REMOTE_HOST "GET /SOGo/saml2-metadata HTTP/1.1" 404 43/0 0.080 - - 3M

It appears as though there is something missing from the packages.