The Appian server started facing a problem with its hard disk getting full. The

danny.leo

Certified Associate Developer

over 10 years ago

The Appian server started facing a problem with its hard disk getting full. The hard disk was cleaned up and freed up the server space. Then the KDBs refused to start. However, we did check-pointing and restored to earlier KDBs. After this the KDBs came through.

After this, the JBOSS started, but did not load the Appian Wars. As a result Appian Login page do not come up. Giving an 404. JBOSS is not giving any error any any logs as well.

Any thoughts?

Discussion posts and replies are publicly visible

0 Alok Mohare
Appian Employee
over 10 years ago

Does check-engine show all Appian Engines are up?

Can you attach the complete server.log from the last restart of JBoss (<JBOSS_HOME>\\standalone\\log)?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 danny.leo
Certified Associate Developer
over 10 years ago

Check engine shows Ok for all. (server log attached)
server.log
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 danny.leo
Certified Associate Developer
over 10 years ago

Quick Update: After running the Config Manager the JBOSS is loading the Appian war now. However it is throwing an exception... It is not able to find the Primary Data Source. We think it is picking up the wrong name possibly? I'll attach a new log momentarily.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 danny.leo
Certified Associate Developer
over 10 years ago

new server log (most recent) attached. Thanks for you help!!!
server.log
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 nathan.schmitz
Certified Associate Developer
over 10 years ago

It seems like you have an authentication issue.

From your logs:
Caused by: java.sql.SQLException: Access denied for user 'appian'@'localhost' (using password: YES)
          at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1094)
          at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4226)
          at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4158)
          at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:926)

Validate that the datasource is configured correctly and that you've configured the passwords properly.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 danny.leo
Certified Associate Developer
over 10 years ago

Thanks for all the help Nathan and Alok! Everything is perfect now!!!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel