I have issue with dataservices in EI6.3.0 related to timezone. I am in: Central European Time (CET) +0100 UTC (Daylight Saving Time). When I invoke "select sysdate from dual" I still getting wrong time - 1 hour after my current time. For example when is 9.00 PM I get response 10.00 PM. I have WSO2 AS 5.2.1 and there is no issue with time. I tried serveral solution like :
-Ddss.legacy.timezone.mode=true but none of them is working. Can you help me?
I solved this issue by adding: Ddss.legacy.timezone.mode=true to both configuration:
...\wso2ei-6.3.0\bin\integrator.bat
...\wso2ei-6.3.0\yajsw-stable-11.11\conf\wrapper.conf
Previously I forgot to add this entry to wrapper.conf cause I run WSO2 as windows service.
Related
I am trying to set up an application as a service on OpenSUSE LEAP 15.
Googling around I found that one does that (or should I say "one can do that"?) by providing a file <servicename>.service in /usr/lib/systemd/system/ and then one enables that service using YaST.
I provided such a file (copying from a tomcat.service file already on the machine and replacing the misc. entries with values relevant for my application).
The setup using YaST seemed to have worked OK, the service was listed and I enabled it. But now I have an issue: when I start the application using service <servicename> start the startup fails. Using service <servicename> status I see the last 10 lines of some log which read:
Jun 08 14:41:04 test-vm ctlscript.sh[31955]: at java.lang.reflect.Method.invoke(Method.java:498)
Jun 08 14:41:04 test-vm ctlscript.sh[31955]: at org.apache.catalina.startup.Bootstrap.stopServer(Bootstrap.java:371)
Jun 08 14:41:04 test-vm ctlscript.sh[31955]: at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:458)
...
This is the tail of some Java stacktrace, so obviously there is some exception while starting up.
But to be able to figure out what is going wrong I would need to see more from that log but where is this service command logging to? I.e. from which logfile does the above content of the service ... status command come from?
Ah - I finally found the solution: one can use journalctl -u <servicename> to see all log entries of a specific service. While that doesn't answer the original question it serves the underlying purpose of the question, namely to see all log entries for a specific service.
AWS polly polly.us-east-2.amazonaws.com/v1/speech does not work on ubuntu 16 server and returns 403 forbidden but it works on 18 ubuntu and returns 200 OK.
I am facing this issue and wired to understand the reason behind it.
What can be reason behind it ? And how to solve this issue ?
Dear guys,
Finally I got the actual reason behind it. I checked today and found it was due to the next date set 15 MAY, 15:10:00" at this Ubuntu 16 server. When I changed to today's date time and tested it. The api was fired with 200,OK.
Actually current date time is used in calculating AWS Signature 4 Code so it could not be matched with AWS server side in a particular region.
Below are the logs::
root#abc:/usr/local/vvv/Demo_Project# date
Sat May 15 15:07:09 IST 2021
root#abc:/usr/local/vvv/Demo_Project# java -jar AWSTTS.jar
AWS jsonString Format :: 2021-05-15 15:07:17.482
2021-05-15 15:07:18.981
AWS ResponseCode & ResponseMessage :: 403 Forbidden
3. 2021-05-15 15:07:19.229
root#abc:/usr/local/vvv/Demo_Project# date -s "14 MAY 2021 15:07:00"
Fri May 14 15:07:00 IST 2021
root#abc:/usr/local/vvv/Demo_Project# java -jar AWSTTS.jar
AWS jsonString Format :: 2021-05-14 15:07:04.650
2021-05-14 15:07:04.653
AWS ResponseCode & ResponseMessage :: 200 OK
3. 2021-05-14 15:07:06.295
after pressing update service software release in AWS console the following message appeared An update to release *******has been requested and is pending.
Before the update starts, you can cancel it any time."
Right now I waited for 1 day - still pending.
Any ideas how much time does it take, or do i need to do anything to move it from pending to updating, and should i expect any downtime in the update processenter image description here
I requested the R20210426-P2 update on a Monday and it was completed on the next Saturday so roughly 6 days from request to actual update. It's also worth noting that the update does not show up in the Upgrade tab in the UI, it shows up in the Notifications tab with this:
Service software update R20210426-P2 completed.
[UPDATE 11 Jul 2021] I just proceeded with updates on two additional domains and the updates began within 15 minutes.
[UPDATE 17 Dec 2021 Log4J CVE] I've had variable luck with the R20211203-P2. One cluster updated in a few hours and one took a few days. A third I was sure I started a few days ago but it gave me the option to update today (possibly a timeout?). I'm guessing they limit the number of concurrent updates and things are backed up. I recommend continuing to check the console but have patience, they do eventually get updated. If you have paid support, definitely open a ticket.
I have a simple task schedule that sends a email for test.
It's not working at all,looking at the logs:
scheduler.log
Jul 8, 2016 1:20 PM Information scheduler-1
[test] Executing at Fri Jul 08 13:20:00 PDT 2016
It shows that it has run, and I also think its not running other task.
Looking at the application log I also see no errors.
Is there any other place I should be looking at?
The log you show above indicates if the scheduler ran if expected. It does not indicate if you page you ran was success.
To find out what happened with the page, go the the scheduled task editor and "Save output to a file".
Then specify a file name. Depending on the nature of the scheduled task, you may want to publish to a shared directory, or keep it hidden way.
Make sure to choose "Overwrite" so that you can always get the latest result of your scheduled task.
<RequestTime>Mon, 14 Mar 2011 10:09:28 GMT</RequestTime>
<ServerTime>2011-03-14T09:09:29Z</ServerTime></Error>
reason: The reason of this problem is that Amazon S3 allows only a small time stamp variation up to 15 minutes between the server and its requesting client (user pc). As Amazon is a big backup server of large number of users, security does matter a lot.
solution: I installed ntp on my ubuntu machine and try to sync it with s3. But still throwing same error.
How can I solved it.
My project is in Django
Make sure you use UTC time for your requests. From the AWS docs:
Request Elements
Time stamp—Each request must contain the date and time the request
was created, represented as a string
in UTC.
I had the same problem: Update your date with the following:
rdate -s ntp.xs4all.nl
substitute with whatever ntp server you require.