Schedule issues
@hk0 wrote: Hi, I m facing issues in schedules. I have a user in the Asia/Dubai timezone that has created a schedule for Thu., Oct. 17 2019, 1:00 AM Asia/Dubai timezone, custom repeat every 4 weeks on...
View ArticleSchedule issues
@Lukas wrote: Please check the previous answers. I think this is your problem: Timezone of scans Greenbone Community Edition (GCE) VM How can I set the timezone of the VM? my scan reports show the...
View ArticleSchedule issues
@hk0 wrote: I’m sorry, I may have been too imprecise. The mentioned user account has the timezone Asia/Dubai applied and the schedule set up in that timezone as well. The issue is that the next run is...
View ArticleSchedule issues
@Lukas wrote: As suggested in the post you must run your OS in UTC and setup the user timezone within the GSA everything else will shift the UTC timezone and mess your schedules up. Please read the...
View ArticleSchedule issues
@bricks wrote: Do debug this issue please open the details page of the wrong displayed scheduled and take a look at the http requests of the details page. There should be some request with...
View ArticleSchedule issues
@hk0 wrote: I do unfortunately not see any such request on the details page … Am I looking at the wrong spot Read full topic
View ArticleSchedule issues
@bricks wrote: You have to open the developer tools of your browser. For chrome: https://developers.google.com/web/tools/chrome-devtools/network/reference Read full topic
View ArticleSchedule issues
@hk0 wrote: This seems to be the interesting response: <first_time>2019-10-17T01:00:00+04:00</first_time> <next_time>2019-11-08T01:00:00+04:00</next_time> BEGIN:VCALENDAR...
View ArticleSchedule issues
@hk0 wrote: I have not noted that the OS needs to run in UTC in addition to the fact that everything internally is UTC. I have earlier today changed the OS to run in UTC but with no change in the...
View ArticleSchedule issues
@bricks wrote: Your ical data shows the mistake: BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Greenbone.net//NONSGML Greenbone Security Manager 8.0.1//EN BEGIN:VEVENT DTSTART:20191016T210000Z DURATION:PT0S...
View ArticleSchedule issues
@bricks wrote: Just for information hk0: <first_time>2019-10-17T01:00:00+04:00</first_time> <next_time>2019-11-08T01:00:00+04:00</next_time> are both ignored by GSA because...
View ArticleSchedule issues
@hk0 wrote: So if I got you correct that would mean that for recurrence configured in schedules, UTC needs to be considered. In my case I would need to configure BYDAY=WE to have the scan been...
View ArticleSchedule issues
@bricks wrote: The ical data is always stored in UTC because getting the timezone information into the ical data is very very error prone and can lead to a lot of issues. Therefore selecting a weekday...
View ArticleSchedule issues
@hk0 wrote: Well from a users perspective I would call it a bug or at least a huge step back compared to previous versions of OpenVAS/GVM as this has worked like a charm. Anyway, thanks a lot for...
View ArticleSchedule issues
@bricks wrote: Btw. it wasn’t possible to run a schedule on a specific workday before GVM 10. But of course this bug broke the run every X week use case for specific timezones. Read full topic
View Article
More Pages to Explore .....