kaoru watanabe
Rank: #44220
85Views
16Comments
Solved
publish error occurred
Question

An error occurred when trying to publish.
Can you tell me how to solve it?


?ErrorMessage

--------------------------------------------------------------------------------------------------

Error message from node XXXXXXX: Deployment failed

Deployment failed. Unexpected content found in ping. Status: OK. Content: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" >

<html>

<head>

<title>ping</title>

</head>

<body>

<p id="XXXXXXXXXXX">OutSystems Platform Server is running</p>

</body>

</html>

CompModule : Broadcast Message

--------------------------------------------------------------------------------------------------


0
0
on 2019-10-07
Copy link to comment
kaoru watanabe
Rank: #44220
Solution

Sudip Dey wrote:

kaoru watanabe wrote:

Sudip Dey wrote:

kaoru watanabe wrote:

Sudip Dey wrote:

Did you check it from the service center as per my instruction?

I checked.
I found a red notification in my deployment, so I'm contacting my contracted support vendor.



Yes you needs to contact with the outsystems support.

Do you have a solution?

This issue only can be resolved by the support team of OutSystems. It needs to wait for a minimum of 2 days (48 hours) to get a response from the Support. Please be patients until they respond. This is the only solution in this case. I hope this will help you,

Thank you,

Sudip

I solved it myself.
Since the write permission of the deployment folder has changed, it was Granted write permission again.


See solution in context
2
0
on 2019-12-06
Copy link to comment
Sudip Dey
Rank: #204

Hi,

Go to the service center and click on the Monitoring Tab and then click on the Environment Health. Check there if anything is wrong there. If you find any red or yellow notification, then you have to contact with Outsystems Support to resolve it. 


Thank you,

Sudip

0
0
on 2019-10-07
Copy link to comment
Daniel Gravito
Rank: #7088

kaoru watanabe wrote:

An error occurred when trying to publish.
Can you tell me how to solve it?


?ErrorMessage

--------------------------------------------------------------------------------------------------

Error message from node XXXXXXX: Deployment failed

Deployment failed. Unexpected content found in ping. Status: OK. Content: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" >

<html>

<head>

<title>ping</title>

</head>

<body>

<p id="XXXXXXXXXXX">OutSystems Platform Server is running</p>

</body>

</html>

CompModule : Broadcast Message

--------------------------------------------------------------------------------------------------


Do you have access to front end server?


0
0
on 2019-10-07
Copy link to comment
kaoru watanabe
Rank: #44220

Daniel Gravito wrote:

kaoru watanabe wrote:

An error occurred when trying to publish.
Can you tell me how to solve it?


?ErrorMessage

--------------------------------------------------------------------------------------------------

Error message from node XXXXXXX: Deployment failed

Deployment failed. Unexpected content found in ping. Status: OK. Content: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" >

<html>

<head>

<title>ping</title>

</head>

<body>

<p id="XXXXXXXXXXX">OutSystems Platform Server is running</p>

</body>

</html>

CompModule : Broadcast Message

--------------------------------------------------------------------------------------------------


Do you have access to front end server?



It is accessible.

0
0
on 2019-10-07
Copy link to comment
Sudip Dey
Rank: #204

Did you check it from the service center as per my instruction?

0
0
on 2019-10-07
Copy link to comment
kaoru watanabe
Rank: #44220

Sudip Dey wrote:

Did you check it from the service center as per my instruction?

I checked.
I found a red notification in my deployment, so I'm contacting my contracted support vendor.


0
0
on 2019-10-07
Copy link to comment
Sudip Dey
Rank: #204

kaoru watanabe wrote:

Sudip Dey wrote:

Did you check it from the service center as per my instruction?

I checked.
I found a red notification in my deployment, so I'm contacting my contracted support vendor.



Yes you needs to contact with the outsystems support.

0
0
on 2019-10-07
Copy link to comment
kaoru watanabe
Rank: #44220

Sudip Dey wrote:

kaoru watanabe wrote:

Sudip Dey wrote:

Did you check it from the service center as per my instruction?

I checked.
I found a red notification in my deployment, so I'm contacting my contracted support vendor.



Yes you needs to contact with the outsystems support.

Do you have a solution?


0
0
on 2019-10-07
Copy link to comment
Sudip Dey
Rank: #204

kaoru watanabe wrote:

Sudip Dey wrote:

kaoru watanabe wrote:

Sudip Dey wrote:

Did you check it from the service center as per my instruction?

I checked.
I found a red notification in my deployment, so I'm contacting my contracted support vendor.



Yes you needs to contact with the outsystems support.

Do you have a solution?

This issue only can be resolved by the support team of OutSystems. It needs to wait for a minimum of 2 days (48 hours) to get a response from the Support. Please be patients until they respond. This is the only solution in this case. I hope this will help you,

Thank you,

Sudip

0
0
on 2019-10-09
Copy link to comment
kaoru watanabe
Rank: #44220
Solution

Sudip Dey wrote:

kaoru watanabe wrote:

Sudip Dey wrote:

kaoru watanabe wrote:

Sudip Dey wrote:

Did you check it from the service center as per my instruction?

I checked.
I found a red notification in my deployment, so I'm contacting my contracted support vendor.



Yes you needs to contact with the outsystems support.

Do you have a solution?

This issue only can be resolved by the support team of OutSystems. It needs to wait for a minimum of 2 days (48 hours) to get a response from the Support. Please be patients until they respond. This is the only solution in this case. I hope this will help you,

Thank you,

Sudip

I solved it myself.
Since the write permission of the deployment folder has changed, it was Granted write permission again.


2
0
on 2019-10-11
Copy link to comment
Job Smeets
Rank: #25511

kaoru watanabe wrote:

Sudip Dey wrote:

kaoru watanabe wrote:

Sudip Dey wrote:

kaoru watanabe wrote:

Sudip Dey wrote:

Did you check it from the service center as per my instruction?

I checked.
I found a red notification in my deployment, so I'm contacting my contracted support vendor.



Yes you needs to contact with the outsystems support.

Do you have a solution?

This issue only can be resolved by the support team of OutSystems. It needs to wait for a minimum of 2 days (48 hours) to get a response from the Support. Please be patients until they respond. This is the only solution in this case. I hope this will help you,

Thank you,

Sudip

I solved it myself.
Since the write permission of the deployment folder has changed, it was Granted write permission again.


Kaoru, thank you for this one, that helped us find the issue! 

However, I was wondering whether you ran the configuration tool after your JBoss update? We did not run it, as the platform seemed to be working fine, but upon reading its contents, I see a lot of references to changing ownership and rights to multiple directories and files on the filesystem.

We will be testing this after publishing our solution and update this thread.


0
0
on 2019-12-06
Copy link to comment
JOHN CASTRO
Rank: #28315

Replying to kaoru watanabe's comment on 11 Oct 2019 05:33:54

could you explain the folder that you changed permissions? thanks

0
0
on 4th Feb
Copy link to comment
Job Smeets
Rank: #25511

Replying to JOHN CASTRO's comment on 04 Feb 2021 21:28:37

Hi John,

Sorry, we've migrated from the Java stack to the .NET stack in the meantime so I'm not sure and can't check anymore. Looking back at this topic, I assume it must have been the /running/ folder in the JBoss home directory.

Hope it helps

0
0
on 5th Feb
Copy link to comment
Sudip Dey
Rank: #204

Please check it

0
0
on 2019-10-07
Copy link to comment
kaoru watanabe
Rank: #44220

Supplement

Since JBossEAP was a security vulnerability, a minor version upgrade of JBoss EAP was performed.

As a result, deployment is no longer possible.

We are currently identifying the package that is causing the problem.


¦security vulnerability

Red Hat Update for JBoss Core Services (RHSA-2017:2710)
Red Hat Update for JBoss Enterprise Application Platform 6.4.19 (RHSA-2018:0270)
Red Hat Update for JBoss Enterprise Application Platform 6.4 (RHSA-2018:0627)
Red Hat Update for JBoss Enterprise Application Platform 6.4.20 (RHSA-2018:1449)
Red Hat Update for Red Hat JBoss Enterprise Application Platform 6.4.21 (RHSA-2018:2743)
Red Hat Update for Red Hat JBoss Core Services Apache HTTP Server 2.4.29 (RHSA-2019:0367)

1
0
on 2019-10-07
Copy link to comment
kaoru watanabe
Rank: #44220

kaoru watanabe wrote:

Supplement

Since JBossEAP was a security vulnerability, a minor version upgrade of JBoss EAP was performed.

As a result, deployment is no longer possible.

We are currently identifying the package that is causing the problem.


¦security vulnerability

Red Hat Update for JBoss Core Services (RHSA-2017:2710)
Red Hat Update for JBoss Enterprise Application Platform 6.4.19 (RHSA-2018:0270)
Red Hat Update for JBoss Enterprise Application Platform 6.4 (RHSA-2018:0627)
Red Hat Update for JBoss Enterprise Application Platform 6.4.20 (RHSA-2018:1449)
Red Hat Update for Red Hat JBoss Enterprise Application Platform 6.4.21 (RHSA-2018:2743)
Red Hat Update for Red Hat JBoss Core Services Apache HTTP Server 2.4.29 (RHSA-2019:0367)


It turns out that an error occurs when any of the following is applied.

--- --- --- --- ---

jbossas-appclient
jbossas-bundles
jbossas-core
jbossas-domain
jbossas-modules-eap
jbossas-product-eap
jbossas-standalone
jbossas-welcome-content-eap
jbcs-httpd24-runtime

--- --- --- --- ---

0
0
on 2019-10-07
Copy link to comment
kaoru watanabe
Rank: #44220

kaoru watanabe wrote:

kaoru watanabe wrote:

Supplement

Since JBossEAP was a security vulnerability, a minor version upgrade of JBoss EAP was performed.

As a result, deployment is no longer possible.

We are currently identifying the package that is causing the problem.


¦security vulnerability

Red Hat Update for JBoss Core Services (RHSA-2017:2710)
Red Hat Update for JBoss Enterprise Application Platform 6.4.19 (RHSA-2018:0270)
Red Hat Update for JBoss Enterprise Application Platform 6.4 (RHSA-2018:0627)
Red Hat Update for JBoss Enterprise Application Platform 6.4.20 (RHSA-2018:1449)
Red Hat Update for Red Hat JBoss Enterprise Application Platform 6.4.21 (RHSA-2018:2743)
Red Hat Update for Red Hat JBoss Core Services Apache HTTP Server 2.4.29 (RHSA-2019:0367)


It turns out that an error occurs when any of the following is applied.

--- --- --- --- ---

jbossas-appclient
jbossas-bundles
jbossas-core
jbossas-domain
jbossas-modules-eap
jbossas-product-eap
jbossas-standalone
jbossas-welcome-content-eap
jbcs-httpd24-runtime

--- --- --- --- ---


When jbossas-standalone version was upgraded, a bug came out.

0
0
on 2019-10-08
Copy link to comment